diff --git a/website/content/docs/concepts/security.mdx b/website/content/docs/concepts/security.mdx index b3f0bcec5..221f52379 100644 --- a/website/content/docs/concepts/security.mdx +++ b/website/content/docs/concepts/security.mdx @@ -17,7 +17,7 @@ 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 +Consul](https://developer.hashicorp.com/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). diff --git a/website/content/docs/concepts/variables.mdx b/website/content/docs/concepts/variables.mdx index ebd89db33..231ae6156 100644 --- a/website/content/docs/concepts/variables.mdx +++ b/website/content/docs/concepts/variables.mdx @@ -155,7 +155,7 @@ nomad acl policy apply \ See [Workload Associated ACL Policies] for more details. [HashiCorp Consul]: https://www.consul.io/ -[HashiCorp Vault]: https://vaultproject.io +[HashiCorp Vault]: https://www.vaultproject.io/ [Key Management]: /docs/operations/key-management [ACL policy specification]: /docs/other-specifications/acl-policy [`template`]: /docs/job-specification/template diff --git a/website/content/docs/configuration/consul.mdx b/website/content/docs/configuration/consul.mdx index 1e9e36757..6858a2d5e 100644 --- a/website/content/docs/configuration/consul.mdx +++ b/website/content/docs/configuration/consul.mdx @@ -90,13 +90,13 @@ configuring Nomad to talk to Consul via DNS such as consul.service.consul - `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/config/config-files#_grpc_port) + Consul does not enable the [`grpc`](https://developer.hashicorp.com/consul/docs/agent/config/config-files#_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) +- `namespace` `(string: "")` - Specifies the [Consul namespace](https://developer.hashicorp.com/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. diff --git a/website/content/docs/configuration/vault.mdx b/website/content/docs/configuration/vault.mdx index 825366878..b4d614cc8 100644 --- a/website/content/docs/configuration/vault.mdx +++ b/website/content/docs/configuration/vault.mdx @@ -86,7 +86,7 @@ vault { - `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) + Visit the [Vault Integration Guide](/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 @@ -149,4 +149,4 @@ 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' +[nomad-vault]: /docs/integrations/vault-integration 'Nomad Vault Integration' diff --git a/website/content/docs/faq.mdx b/website/content/docs/faq.mdx index a229c3839..5465692eb 100644 --- a/website/content/docs/faq.mdx +++ b/website/content/docs/faq.mdx @@ -96,7 +96,7 @@ machine you will need to use the network interface IP address. $ curl http://192.168.0.10:8080 ``` -[consul_dc]: https://www.consul.io/docs/agent/config/config-files#datacenter +[consul_dc]: https://developer.hashicorp.com/consul/docs/agent/config/config-files#datacenter [consul_fed]: https://learn.hashicorp.com/tutorials/consul/federarion-gossip-wan [nomad_region]: /docs/configuration#datacenter [`bootstrap_expect`]: /docs/configuration/server#bootstrap_expect diff --git a/website/content/docs/install/index.mdx b/website/content/docs/install/index.mdx index 59ea11785..ee3e52a77 100644 --- a/website/content/docs/install/index.mdx +++ b/website/content/docs/install/index.mdx @@ -266,7 +266,7 @@ as a copy of [`git`](https://www.git-scm.com/) in your `PATH`. [consul-dev]: https://learn.hashicorp.com/consul/getting-started/agent#starting-the-agent -[consul-download]: https://www.consul.io/downloads +[consul-download]: https://developer.hashicorp.com/consul/downloads [destroy]: https://www.vagrantup.com/docs/cli/destroy diff --git a/website/content/docs/integrations/consul-connect.mdx b/website/content/docs/integrations/consul-connect.mdx index c5ad8a714..75e314c02 100644 --- a/website/content/docs/integrations/consul-connect.mdx +++ b/website/content/docs/integrations/consul-connect.mdx @@ -11,7 +11,7 @@ description: >- ~> **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 +[Consul service mesh](https://developer.hashicorp.com/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 @@ -350,5 +350,5 @@ dashes (`-`) are converted to underscores (`_`) in environment variables so [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`]: https://www.consul.io/docs/security/acl/acl-tokens#token-attributes -[anon_token]: https://www.consul.io/docs/security/acl/acl-tokens#special-purpose-tokens +[`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 diff --git a/website/content/docs/integrations/consul-integration.mdx b/website/content/docs/integrations/consul-integration.mdx index 67a6cfa5b..e2a287448 100644 --- a/website/content/docs/integrations/consul-integration.mdx +++ b/website/content/docs/integrations/consul-integration.mdx @@ -125,9 +125,9 @@ service_prefix "" { [consul]: https://www.consul.io/ "Consul by HashiCorp" -[consul_acls]: https://www.consul.io/docs/security/acl +[consul_acls]: https://developer.hashicorp.com/consul/docs/security/acl -[consul_namespaces]: https://www.consul.io/docs/enterprise/namespaces +[consul_namespaces]: https://developer.hashicorp.com/consul/docs/enterprise/namespaces [consul_agent_namespace]: /docs/configuration/consul#namespace diff --git a/website/content/docs/job-specification/check.mdx b/website/content/docs/job-specification/check.mdx index 70f8bf04e..8fbe335fd 100644 --- a/website/content/docs/job-specification/check.mdx +++ b/website/content/docs/job-specification/check.mdx @@ -435,7 +435,7 @@ Output = nomad: Get "http://:9999/": dial tcp :9999: connect: connection re [check_restart_stanza]: /docs/job-specification/check_restart -[consul_passfail]: https://www.consul.io/docs/discovery/checks#success-failures-before-passing-critical +[consul_passfail]: https://developer.hashicorp.com/consul/docs/discovery/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 diff --git a/website/content/docs/job-specification/connect.mdx b/website/content/docs/job-specification/connect.mdx index 41bc2477f..835f39f80 100644 --- a/website/content/docs/job-specification/connect.mdx +++ b/website/content/docs/job-specification/connect.mdx @@ -50,7 +50,7 @@ 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. + [Connect Native](https://developer.hashicorp.com/consul/docs/connect/native) applications. - `sidecar_service` - ([sidecar_service][]: nil) - This is used to configure the sidecar service created by Nomad for Consul Connect. @@ -66,7 +66,7 @@ or `gateway` may be realized per `connect` block. ### Using Connect Native The following example is a minimal service stanza for a -[Consul Connect Native](https://www.consul.io/docs/connect/native) +[Consul Connect Native](https://developer.hashicorp.com/consul/docs/connect/native) application implemented by a task named `generate`. ```hcl @@ -249,7 +249,7 @@ job "ingress-demo" { [job]: /docs/job-specification/job "Nomad job Job Specification" -[native]: https://www.consul.io/docs/connect/native +[native]: https://developer.hashicorp.com/consul/docs/connect/native [service_task]: /docs/job-specification/service#task-1 "Nomad service task" diff --git a/website/content/docs/job-specification/expose.mdx b/website/content/docs/job-specification/expose.mdx index 17fe8b47c..e7b5396e0 100644 --- a/website/content/docs/job-specification/expose.mdx +++ b/website/content/docs/job-specification/expose.mdx @@ -229,7 +229,7 @@ check { ``` [network-to]: /docs/job-specification/network#to -[consul-expose-path-config]: https://www.consul.io/docs/connect/registration/service-registration#expose-paths-configuration-reference +[consul-expose-path-config]: https://developer.hashicorp.com/consul/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' diff --git a/website/content/docs/job-specification/gateway.mdx b/website/content/docs/job-specification/gateway.mdx index 0ca7cd931..7dcfbe80c 100644 --- a/website/content/docs/job-specification/gateway.mdx +++ b/website/content/docs/job-specification/gateway.mdx @@ -10,15 +10,15 @@ description: |- -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) +The `gateway` stanza allows configuration of [Consul Connect Gateways](https://developer.hashicorp.com/consul/docs/connect/gateways). Nomad will +automatically create the necessary Gateway [Configuration Entry](https://developer.hashicorp.com/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` stanza. Additional information about Gateway configurations can be found in Consul's -[Connect Gateways](https://www.consul.io/docs/connect/gateways) documentation. +[Connect Gateways](https://developer.hashicorp.com/consul/docs/connect/gateways) documentation. -~> **Note:** [Ingress Gateways](https://www.consul.io/docs/connect/gateways/ingress-gateway) +~> **Note:** [Ingress Gateways](https://developer.hashicorp.com/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](https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx?in=nomad/load-balancing) provide more suitable features. @@ -101,17 +101,17 @@ envoy_gateway_bind_addresses "" { - `tls_min_version` `(string: optional)` - Set the default minimum TLS version supported by the gateway. Refer to - [`TLSMinVersion`](https://www.consul.io/docs/connect/config-entries/ingress-gateway#tlsminversion) + [`TLSMinVersion`](https://developer.hashicorp.com/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`](https://www.consul.io/docs/connect/config-entries/ingress-gateway#tlsmaxversion) + [`TLSMaxVersion`](https://developer.hashicorp.com/consul/docs/connect/config-entries/ingress-gateway#tlsmaxversion) in the Consul documentation for supported versions. - `cipher_suites` `(array: optional)` - Set the default list of TLS cipher suites for the gateway's listeners. Refer to - [`CipherSuites`](https://www.consul.io/docs/connect/config-entries/ingress-gateway#ciphersuites) + [`CipherSuites`](https://developer.hashicorp.com/consul/docs/connect/config-entries/ingress-gateway#ciphersuites) in the Consul documentation for the supported cipher suites. #### `listener` Parameters @@ -121,7 +121,7 @@ envoy_gateway_bind_addresses "" { 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) + set the [Protocol](https://developer.hashicorp.com/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` (array<[service]>: required) - One or more services to be @@ -648,9 +648,9 @@ job "countdash-mesh-two" { [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/connect/config-entries/service-resolver#connecttimeout -[connect_mesh_gw]: https://www.consul.io/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways#mesh-gateways +[advanced configuration]: https://developer.hashicorp.com/consul/docs/connect/proxies/envoy#advanced-configuration +[connect_timeout_ms]: https://developer.hashicorp.com/consul/docs/connect/config-entries/service-resolver#connecttimeout +[connect_mesh_gw]: https://developer.hashicorp.com/consul/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 @@ -658,7 +658,7 @@ job "countdash-mesh-two" { [listener]: /docs/job-specification/gateway#listener-parameters [interpolation]: /docs/runtime/interpolation [service]: /docs/job-specification/gateway#service-parameters -[service-default]: https://www.consul.io/docs/agent/config-entries/service-defaults +[service-default]: https://developer.hashicorp.com/consul/docs/connect/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/website/content/docs/job-specification/proxy.mdx b/website/content/docs/job-specification/proxy.mdx index fce984bf6..0f256f0cb 100644 --- a/website/content/docs/job-specification/proxy.mdx +++ b/website/content/docs/job-specification/proxy.mdx @@ -58,11 +58,11 @@ job "countdash" { - `upstreams` ([upstreams][]: nil) - Used to configure details of each upstream service that this sidecar proxy communicates with. - `expose` ([expose]: nil) - 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) + See Consul's [Expose Paths Configuration Reference](https://developer.hashicorp.com/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](https://www.consul.io/docs/connect/proxies/envoy#dynamic-configuration) + documentation](https://developer.hashicorp.com/consul/docs/connect/proxies/envoy#dynamic-configuration) for details. Keys and values support [runtime variable interpolation][interpolation]. ## `proxy` Examples diff --git a/website/content/docs/job-specification/service.mdx b/website/content/docs/job-specification/service.mdx index 2fb6861ab..91bc66590 100644 --- a/website/content/docs/job-specification/service.mdx +++ b/website/content/docs/job-specification/service.mdx @@ -137,7 +137,7 @@ Connect][connect] integration. - `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) + [documentation](https://developer.hashicorp.com/consul/docs/concepts/anti-entropy#enable-tag-override) for more information. Only available where `provider = "consul"`. - `address` `(string: )` - Specifies a custom address to advertise in @@ -501,8 +501,8 @@ 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-docs/agent/check#grpc -[consul_passfail]: https://www.consul.io/docs/agent/checks#success-failures-before-passing-critical +[consul_grpc]: https://developer.hashicorp.com/consul/api-docs/agent/check#grpc +[consul_passfail]: https://developer.hashicorp.com/consul/docs/discovery/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' @@ -516,4 +516,4 @@ advertise and check directly since Nomad isn't managing any port assignments. [service_task]: /docs/job-specification/service#task-1 [network_mode]: /docs/job-specification/network#mode [on_update]: /docs/job-specification/service#on_update -[tagged_addresses]: https://www.consul.io/docs/discovery/services#tagged-addresses \ No newline at end of file +[tagged_addresses]: https://developer.hashicorp.com/consul/docs/discovery/services#tagged-addresses \ No newline at end of file diff --git a/website/content/docs/job-specification/task.mdx b/website/content/docs/job-specification/task.mdx index d256c67c2..e68f95035 100644 --- a/website/content/docs/job-specification/task.mdx +++ b/website/content/docs/job-specification/task.mdx @@ -215,7 +215,7 @@ task "server" { [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' +[rkt]: /plugins/drivers/community/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 diff --git a/website/content/docs/job-specification/upstreams.mdx b/website/content/docs/job-specification/upstreams.mdx index 87b708eb0..b1613c9d6 100644 --- a/website/content/docs/job-specification/upstreams.mdx +++ b/website/content/docs/job-specification/upstreams.mdx @@ -133,6 +133,6 @@ and a local bind port. [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 +[service_defaults_mode]: https://developer.hashicorp.com/consul/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/service-to-service-traffic-datacenters#mesh-gateways +[mesh_gateways]: https://developer.hashicorp.com/consul/docs/connect/gateways/mesh-gateway/service-to-service-traffic-datacenters#mesh-gateways diff --git a/website/content/docs/operations/index.mdx b/website/content/docs/operations/index.mdx index fe70c7ebf..f9e1dbfa4 100644 --- a/website/content/docs/operations/index.mdx +++ b/website/content/docs/operations/index.mdx @@ -12,7 +12,7 @@ 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) +- [Telemetry Overview](/docs/operations/monitoring-nomad) - [Metrics](/docs/operations/metrics-reference) - [Cluster Management](https://learn.hashicorp.com/collections/nomad/manage-clusters) - [Transport Security](https://learn.hashicorp.com/collections/nomad/transport-security) diff --git a/website/content/docs/operations/monitoring-nomad.mdx b/website/content/docs/operations/monitoring-nomad.mdx index 69545748f..aafc0c443 100644 --- a/website/content/docs/operations/monitoring-nomad.mdx +++ b/website/content/docs/operations/monitoring-nomad.mdx @@ -292,14 +292,14 @@ 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 +[allocation-metrics]: /docs/operations/metrics-reference#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 +[metric-types]: /docs/operations/metrics-reference#metric-types [metrics-api-endpoint]: /api-docs/metrics [prometheus-telem]: /docs/configuration/telemetry#prometheus [`plan_rejection_tracker`]: /docs/configuration/server#plan_rejection_tracker @@ -307,7 +307,7 @@ latency and packet loss for the [Serf] address. [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 +[tagged-metrics]: /docs/operations/metrics-reference#tagged-metrics [telemetry-stanza]: /docs/configuration/telemetry [Consensus Protocol (Raft)]: /docs/operations/monitoring-nomad#consensus-protocol-raft [Job Summary Metrics]: /docs/operations/metrics-reference#job-summary-metrics diff --git a/website/content/docs/runtime/environment.mdx b/website/content/docs/runtime/environment.mdx index 90ed25160..26fc38fa9 100644 --- a/website/content/docs/runtime/environment.mdx +++ b/website/content/docs/runtime/environment.mdx @@ -113,6 +113,6 @@ 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' +[vault]: /docs/integrations/vault-integration 'Nomad Vault Integration' [filesystem internals]: /docs/concepts/filesystem [`env.denylist`]: /docs/configuration/client#env-denylist diff --git a/website/content/docs/runtime/interpolation.mdx b/website/content/docs/runtime/interpolation.mdx index ec3c93133..1a4c221fd 100644 --- a/website/content/docs/runtime/interpolation.mdx +++ b/website/content/docs/runtime/interpolation.mdx @@ -63,227 +63,37 @@ Below is a full listing of node attributes that are interpretable. These attributes are interpreted by **both** constraints and within the task and driver. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
VariableDescriptionExample 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'} -
+| 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 given by `property` on the client | `${attr.cpu.arch} => amd64` | +| `${meta.}` | Metadata value given by `key` on the client | `${meta.foo} => bar` | Below is a table documenting common node properties: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
PropertyDescription
- {'${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 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
+| 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.}` | See the [task drivers](/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]`. diff --git a/website/content/docs/upgrade/upgrade-specific.mdx b/website/content/docs/upgrade/upgrade-specific.mdx index c9f310fc1..2cbbbf66e 100644 --- a/website/content/docs/upgrade/upgrade-specific.mdx +++ b/website/content/docs/upgrade/upgrade-specific.mdx @@ -1521,8 +1521,8 @@ deleted and then Nomad 0.3.0 can be launched. [cap_drop_exec]: /docs/drivers/exec#cap_drop [`log_file`]: /docs/configuration#log_file [Upgrading to Raft Protocol 3]: /docs/upgrade#upgrading-to-raft-protocol-3 -[`Local`]: https://www.consul.io/docs/security/acl/acl-tokens#token-attributes -[anon_token]: https://www.consul.io/docs/security/acl/acl-tokens#special-purpose-tokens +[`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_acl]: https://github.com/hashicorp/consul/issues/7414 [kill_timeout]: /docs/job-specification/task#kill_timeout [max_kill_timeout]: /docs/configuration/client#max_kill_timeout diff --git a/website/content/partials/envvars.mdx b/website/content/partials/envvars.mdx index d80a4288e..a2987a2a7 100644 --- a/website/content/partials/envvars.mdx +++ b/website/content/partials/envvars.mdx @@ -1,392 +1,47 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
VariableDescription
- NOMAD_ALLOC_DIR - - The path to the shared alloc/ directory. See - here for more information. -
- NOMAD_TASK_DIR - - The path to the task local/ directory. See - here for more information. -
- NOMAD_SECRETS_DIR - - Path to the task's secrets directory. See - here 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
- NOMAD_ALLOC_INDEX - - 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. -
- 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>} - - which are keys in the node's metadata. -
- VAULT_TOKEN - - The task's Vault token. See - Vault Integration - for more details -
Network-related Variables
- NOMAD_IP_<label> - - Host IP for the given port label. See - here 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 - here 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 - here 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_UPSTREAM_PORT_<service> - - Port for the given service when defined as a Consul Connect - upstream. -
- NOMAD_UPSTREAM_ADDR_<service> - - Host IP:Port for the given service when - defined as a Consul Connect - 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 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. -
Consul-related Variables (only set for connect native tasks)
- 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. -
+| Variable | Description | +| ------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `NOMAD_ALLOC_DIR` | The path to the shared `alloc/` directory. See [here](/docs/runtime/environment#task-directories) for more information. | +| `NOMAD_TASK_DIR` | The path to the task `local/` directory. See [here](/docs/runtime/environment#task-directories) for more information. | +| `NOMAD_SECRETS_DIR` | Path to the task's secrets directory. See [here](/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 | +| `NOMAD_ALLOC_INDEX` | 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. | +| `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_` | The metadata value given by `key` on the task's metadata. Note that this is different from [`${meta.}`](/docs/runtime/interpolation#node-variables-) which are keys in the node's metadata. | +| `VAULT_TOKEN` | The task's Vault token. See [Vault Integration](/docs/vault-integration) for more details | +| **Network-related Variables** | +| `NOMAD_IP_