kemko/nomad
1
0
Fork 0
mirror of https://github.com/kemko/nomad.git synced 2026-01-03 08:55:43 +03:00
Code Issues Packages Projects Releases Wiki Activity

[docs] Update redirects and links for learn.hashicorp.com (#8598)

Browse Source 
* Fix links to ACL guides
* Managing Nomad guide links; links in jsx pages
* job updates guide URLS
* node-drain guide URLS
* outage recovery guide links
* fix guide links - sentinel
* fix guide links - namespaces
* fix guide links - quotas
* fix guide links - autopilot
* more guide links.
* more guide links - continued.
* Updating redirects for learn
* Getting Started
* Load Balancing Guides
* update redirects for ui guide
* Consolidate spark redirects to point to GH repo
* operating job update part 1
* finish operating job links; operations guides links.
* finish guide redirects
* coalesce EOL redirects for spark guides.
* one last link
* Checked links and found a few more stray links
* Found more .htmls
* Fixup links for new HC websites
* Post-merge fixups
* linkcheck caught missing ids
This commit is contained in:
Charlie Voiselle
2020-09-29 12:48:32 -04:00
committed by GitHub
parent 2f3f3136e9
commit fee792d2ad
58 changed files with 411 additions and 417 deletions
Download Patch File Download Diff File Expand all files Collapse all files

467
website/_redirects
View File

@@ -1,162 +1,160 @@
/api/* /api-docs/:splat 200
/docs/telemetry/overview /docs/telemetry 301!
# 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."
/guides/outage.html https://learn.hashicorp.com/tutorials/nomad/outage-recovery 301!
# Nomad Learn Redirects
/intro/getting-started/install.html https://learn.hashicorp.com/nomad/getting-started/install 301!
/intro/getting-started/install https://learn.hashicorp.com/nomad/getting-started/install 301!
/intro/getting-started/running.html https://learn.hashicorp.com/nomad/getting-started/running 301!
/intro/getting-started/running https://learn.hashicorp.com/nomad/getting-started/running 301!
/intro/getting-started/jobs.html https://learn.hashicorp.com/nomad/getting-started/jobs 301!
/intro/getting-started/jobs https://learn.hashicorp.com/nomad/getting-started/jobs 301!
/intro/getting-started/cluster.html https://learn.hashicorp.com/nomad/getting-started/cluster 301!
/intro/getting-started/cluster https://learn.hashicorp.com/nomad/getting-started/cluster 301!
/intro/getting-started/ui.html https://learn.hashicorp.com/nomad/getting-started/ui 301!
/intro/getting-started/ui https://learn.hashicorp.com/nomad/getting-started/ui 301!
/intro/getting-started/next-steps.html https://learn.hashicorp.com/nomad/getting-started/next-steps 301!
/intro/getting-started/next-steps https://learn.hashicorp.com/nomad/getting-started/next-steps 301!
/intro/getting-started/install.html https://learn.hashicorp.com/tutorials/nomad/get-started-install 301!
/intro/getting-started/install https://learn.hashicorp.com/tutorials/nomad/get-started-install 301!
/intro/getting-started/running.html https://learn.hashicorp.com/tutorials/nomad/get-started-run 301!
/intro/getting-started/running https://learn.hashicorp.com/tutorials/nomad/get-started-run 301!
/intro/getting-started/jobs.html https://learn.hashicorp.com/tutorials/nomad/get-started-jobs 301!
/intro/getting-started/jobs https://learn.hashicorp.com/tutorials/nomad/get-started-jobs 301!
/intro/getting-started/cluster.html https://learn.hashicorp.com/tutorials/nomad/get-started-cluster 301!
/intro/getting-started/cluster https://learn.hashicorp.com/tutorials/nomad/get-started-cluster 301!
/intro/getting-started/ui.html https://learn.hashicorp.com/tutorials/nomad/get-started-ui 301!
/intro/getting-started/ui https://learn.hashicorp.com/tutorials/nomad/get-started-ui 301!
/intro/getting-started/next-steps.html https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more 301!
/intro/getting-started/next-steps https://learn.hashicorp.com/tutorials/nomad/get-started-learn-more 301!
/guides/load-balancing https://learn.hashicorp.com/nomad?track=load-balancing#operations-and-development 301!
/guides/load-balancing/fabio.html https://learn.hashicorp.com/nomad/load-balancing/fabio 301!
/guides/load-balancing/fabio https://learn.hashicorp.com/nomad/load-balancing/fabio 301!
/guides/load-balancing/nginx.html https://learn.hashicorp.com/nomad/load-balancing/nginx 301!
/guides/load-balancing/nginx https://learn.hashicorp.com/nomad/load-balancing/nginx 301!
/guides/load-balancing/haproxy.html https://learn.hashicorp.com/nomad/load-balancing/haproxy 301!
/guides/load-balancing/haproxy https://learn.hashicorp.com/nomad/load-balancing/haproxy 301!
/guides/load-balancing/traefik.html https://learn.hashicorp.com/nomad/load-balancing/traefik 301!
/guides/load-balancing/traefik https://learn.hashicorp.com/nomad/load-balancing/traefik 301!
/guides/load-balancing https://learn.hashicorp.com/collections/nomad/load-balancing 301!
/guides/load-balancing/fabio.html https://learn.hashicorp.com/tutorials/nomad/load-balancing-fabio 301!
/guides/load-balancing/fabio https://learn.hashicorp.com/tutorials/nomad/load-balancing-fabio 301!
/guides/load-balancing/nginx.html https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx 301!
/guides/load-balancing/nginx https://learn.hashicorp.com/tutorials/nomad/load-balancing-nginx 301!
/guides/load-balancing/haproxy.html https://learn.hashicorp.com/tutorials/nomad/load-balancing-haproxy 301!
/guides/load-balancing/haproxy https://learn.hashicorp.com/tutorials/nomad/load-balancing-haproxy 301!
/guides/load-balancing/traefik.html https://learn.hashicorp.com/tutorials/nomad/load-balancing-traefik 301!
/guides/load-balancing/traefik https://learn.hashicorp.com/tutorials/nomad/load-balancing-traefik 301!
/guides/stateful-workloads https://learn.hashicorp.com/nomad?track=stateful-workload#operations-and-development 301!
/guides/stateful-workloads/host-volumes.html https://learn.hashicorp.com/nomad/stateful-workloads/host-volumes 301!
/guides/stateful-workloads/host-volumes https://learn.hashicorp.com/nomad/stateful-workloads/host-volumes 301!
/guides/stateful-workloads/portworx.html https://learn.hashicorp.com/nomad/stateful-workloads/portworx 301!
/guides/stateful-workloads/portworx https://learn.hashicorp.com/nomad/stateful-workloads/portworx 301!
/guides/stateful-workloads https://learn.hashicorp.com/collections/nomad/stateful-workloads 301!
/guides/stateful-workloads/host-volumes.html https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-host-volumes 301!
/guides/stateful-workloads/host-volumes https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-host-volumes 301!
/guides/stateful-workloads/portworx.html https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-portworx 301!
/guides/stateful-workloads/portworx https://learn.hashicorp.com/tutorials/nomad/stateful-workloads-portworx 301!
/guides/web-ui https://learn.hashicorp.com/nomad?track=web-ui#getting-started 301!
/guides/web-ui/access.html https://learn.hashicorp.com/nomad/web-ui/access 301!
/guides/web-ui/accessing https://learn.hashicorp.com/nomad/web-ui/access 301!
/guides/web-ui/submitting-a-job.html https://learn.hashicorp.com/nomad/web-ui/ui-workload 301!
/guides/web-ui/submitting-a-job https://learn.hashicorp.com/nomad/web-ui/ui-workload 301!
/guides/web-ui/operating-a-job.html https://learn.hashicorp.com/nomad/web-ui/submit-job 301!
/guides/web-ui/operating-a-job https://learn.hashicorp.com/nomad/web-ui/submit-job 301!
/guides/web-ui/inspecting-the-cluster.html https://learn.hashicorp.com/nomad/web-ui/inspecting-the-cluster 301!
/guides/web-ui/inspecting-the-cluster https://learn.hashicorp.com/nomad/web-ui/inspecting-the-cluster 301!
/guides/web-ui/securing.html https://learn.hashicorp.com/nomad/web-ui/access 301!
/guides/web-ui/securing https://learn.hashicorp.com/nomad/web-ui/access 301!
/guides/web-ui https://learn.hashicorp.com/collections/nomad/web-ui 301!
/guides/web-ui/access.html https://learn.hashicorp.com/tutorials/nomad/web-ui-access 301!
/guides/web-ui/accessing https://learn.hashicorp.com/tutorials/nomad/web-ui-access 301!
/guides/web-ui/submitting-a-job.html https://learn.hashicorp.com/tutorials/nomad/web-ui-workload-info 301!
/guides/web-ui/submitting-a-job https://learn.hashicorp.com/tutorials/nomad/web-ui-workload-info 301!
/guides/web-ui/operating-a-job.html https://learn.hashicorp.com/tutorials/nomad/web-ui-submit-job 301!
/guides/web-ui/operating-a-job https://learn.hashicorp.com/tutorials/nomad/web-ui-submit-job 301!
/guides/web-ui/inspecting-the-cluster.html https://learn.hashicorp.com/tutorials/nomad/web-ui-cluster-info 301!
/guides/web-ui/inspecting-the-cluster https://learn.hashicorp.com/tutorials/nomad/web-ui-cluster-info 301!
/guides/web-ui/securing.html https://learn.hashicorp.com/tutorials/nomad/web-ui-access#access-an-acl-enabled-ui 301!
/guides/web-ui/securing https://learn.hashicorp.com/tutorials/nomad/web-ui-access#access-an-acl-enabled-ui 301!
/guides/governance-and-policy https://learn.hashicorp.com/nomad?track=governance-and-policy#operations-and-development 301!
/guides/governance-and-policy/namespaces.html https://learn.hashicorp.com/nomad/governance-and-policy/namespaces 301!
/guides/governance-and-policy/namespaces https://learn.hashicorp.com/nomad/governance-and-policy/namespaces 301!
/guides/governance-and-policy/quotas.html https://learn.hashicorp.com/nomad/governance-and-policy/quotas 301!
/guides/governance-and-policy/quotas https://learn.hashicorp.com/nomad/governance-and-policy/quotas 301!
/guides/governance-and-policy/sentinel/sentinel-policy.html https://learn.hashicorp.com/nomad/governance-and-policy/sentinel 301!
/guides/governance-and-policy/sentinel/sentinel-policy https://learn.hashicorp.com/nomad/governance-and-policy/sentinel 301!
/guides/governance-and-policy/sentinel/job.html https://learn.hashicorp.com/nomad/governance-and-policy/sentinel 301!
/guides/governance-and-policy/sentinel/job https://learn.hashicorp.com/nomad/governance-and-policy/sentinel 301!
/guides/governance-and-policy https://learn.hashicorp.com/collections/nomad/governance-and-policy 301!
/guides/governance-and-policy/namespaces.html https://learn.hashicorp.com/tutorials/nomad/namespaces 301!
/guides/governance-and-policy/namespaces https://learn.hashicorp.com/tutorials/nomad/namespaces 301!
/guides/governance-and-policy/quotas.html https://learn.hashicorp.com/tutorials/nomad/quotas 301!
/guides/governance-and-policy/quotas https://learn.hashicorp.com/tutorials/nomad/quotas 301!
/guides/governance-and-policy/sentinel/sentinel-policy.html https://learn.hashicorp.com/tutorials/nomad/sentinel 301!
/guides/governance-and-policy/sentinel/sentinel-policy https://learn.hashicorp.com/tutorials/nomad/sentinel 301!
/guides/governance-and-policy/sentinel/job.html https://learn.hashicorp.com/tutorials/nomad/sentinel 301!
/guides/governance-and-policy/sentinel/job https://learn.hashicorp.com/tutorials/nomad/sentinel 301!
/guides/analytical-workloads https://learn.hashicorp.com/nomad?track=spark#spark 301!
/guides/analytical-workloads/index.html https://learn.hashicorp.com/nomad?track=spark#spark 301!
/guides/analytical-workloads/spark/configuration https://learn.hashicorp.com/nomad/spark/configuration 301!
/guides/analytical-workloads/spark/configuration.html https://learn.hashicorp.com/nomad/spark/configuration 301!
/guides/analytical-workloads/spark/customizing https://learn.hashicorp.com/nomad/spark/customizing 301!
/guides/analytical-workloads/spark/customizing.html https://learn.hashicorp.com/nomad/spark/customizing 301!
/guides/analytical-workloads/spark/dynamic https://learn.hashicorp.com/nomad/spark/dynamic 301!
/guides/analytical-workloads/spark/dynamic.html https://learn.hashicorp.com/nomad/spark/dynamic 301!
/guides/analytical-workloads/spark/hdfs https://learn.hashicorp.com/nomad/spark/hdfs 301!
/guides/analytical-workloads/spark/hdfs.html https://learn.hashicorp.com/nomad/spark/hdfs 301!
/guides/analytical-workloads/spark/monitoring https://learn.hashicorp.com/nomad/spark/monitoring 301!
/guides/analytical-workloads/spark/monitoring.html https://learn.hashicorp.com/nomad/spark/monitoring 301!
/guides/analytical-workloads/spark/pre https://learn.hashicorp.com/nomad/spark/pre 301!
/guides/analytical-workloads/spark/pre.html https://learn.hashicorp.com/nomad/spark/pre 301!
/guides/analytical-workloads/spark/resource https://learn.hashicorp.com/nomad/spark/resource 301!
/guides/analytical-workloads/spark/resource.html https://learn.hashicorp.com/nomad/spark/resource 301!
/guides/analytical-workloads/spark/submit https://learn.hashicorp.com/nomad/spark/submit 301!
/guides/analytical-workloads/spark/submit.html https://learn.hashicorp.com/nomad/spark/submit 301!
# Spark guide links are all repointed to deprecated nomad-spark repo
/guides/spark https://github.com/hashicorp/nomad-spark 301!
/guides/spark/* https://github.com/hashicorp/nomad-spark 301!
/guides/analytical-workloads https://github.com/hashicorp/nomad-spark 301! # goes to deprecated page in repo
/guides/analytical-workloads/* https://github.com/hashicorp/nomad-spark 301! # goes to deprecated page in repo
## 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.
#/guides/analytical-workloads/spark/spark.html https://github.com/hashicorp/nomad-spark 301!
#/guides/analytical-workloads/spark/spark https://github.com/hashicorp/nomad-spark 301!
/guides/operating-a-job https://learn.hashicorp.com/nomad?track=managing-jobs#managing-jobs 301!
/guides/operating-a-job/accessing-logs https://learn.hashicorp.com/nomad/managing-jobs/accessing-logs 301!
/guides/operating-a-job/accessing-logs.html https://learn.hashicorp.com/nomad/managing-jobs/accessing-logs 301!
/guides/operating-a-job/configuring-tasks https://learn.hashicorp.com/nomad/managing-jobs/configuring-tasks 301!
/guides/operating-a-job/configuring-tasks.html https://learn.hashicorp.com/nomad/managing-jobs/configuring-tasks 301!
/guides/operating-a-job/external https://learn.hashicorp.com/nomad?track=using-plugins#using-plugins 301!
/guides/operating-a-job/external/index.html https://learn.hashicorp.com/nomad?track=using-plugins#using-plugins 301!
/guides/operating-a-job/external/lxc https://learn.hashicorp.com/nomad/using-plugins/lxc 301!
/guides/operating-a-job/external/lxc.html https://learn.hashicorp.com/nomad/using-plugins/lxc 301!
/guides/operating-a-job/index.html https://learn.hashicorp.com/nomad?track=managing-jobs#managing-jobs 301!
/guides/operating-a-job/inspecting-state https://learn.hashicorp.com/nomad/managing-jobs/inspecting-state 301!
/guides/operating-a-job/inspecting-state.html https://learn.hashicorp.com/nomad/managing-jobs/inspecting-state 301!
/guides/operating-a-job/resource-utilization https://learn.hashicorp.com/nomad/managing-jobs/resource-utilization 301!
/guides/operating-a-job/resource-utilization.html https://learn.hashicorp.com/nomad/managing-jobs/resource-utilization 301!
/guides/operating-a-job/submitting-jobs https://learn.hashicorp.com/nomad/managing-jobs/submitting-jobs 301!
/guides/operating-a-job/submitting-jobs.html https://learn.hashicorp.com/nomad/managing-jobs/submitting-jobs 301!
/guides/operating-a-job/advanced-scheduling/advanced-scheduling https://learn.hashicorp.com/nomad/advanced-scheduling/advanced-scheduling 301!
/guides/operating-a-job/advanced-scheduling/advanced-scheduling.html https://learn.hashicorp.com/nomad/advanced-scheduling/advanced-scheduling 301!
/guides/operating-a-job/advanced-scheduling/affinity https://learn.hashicorp.com/nomad/advanced-scheduling/affinity 301!
/guides/operating-a-job/advanced-scheduling/affinity.html https://learn.hashicorp.com/nomad/advanced-scheduling/affinity 301!
/guides/operating-a-job/advanced-scheduling/preemption-service-batch https://learn.hashicorp.com/nomad/advanced-scheduling/preemption 301!
/guides/operating-a-job/advanced-scheduling/preemption-service-batch.html https://learn.hashicorp.com/nomad/advanced-scheduling/preemption 301!
/guides/operating-a-job/advanced-scheduling/spread https://learn.hashicorp.com/nomad/advanced-scheduling/spread 301!
/guides/operating-a-job/advanced-scheduling/spread.html https://learn.hashicorp.com/nomad/advanced-scheduling/spread 301!
/guides/operating-a-job/failure-handling-strategies https://learn.hashicorp.com/nomad/job-failure-handling/failure-handling 301!
/guides/operating-a-job/failure-handling-strategies/check-restart https://learn.hashicorp.com/nomad/job-failure-handling/check-restart 301!
/guides/operating-a-job/failure-handling-strategies/check-restart.html https://learn.hashicorp.com/nomad/job-failure-handling/check-restart 301!
/guides/operating-a-job/failure-handling-strategies/index.html https://learn.hashicorp.com/nomad/job-failure-handling/failure-handling 301!
/guides/operating-a-job/failure-handling-strategies/reschedule https://learn.hashicorp.com/nomad/job-failure-handling/reschedule 301!
/guides/operating-a-job/failure-handling-strategies/reschedule.html https://learn.hashicorp.com/nomad/job-failure-handling/reschedule 301!
/guides/operating-a-job/failure-handling-strategies/restart https://learn.hashicorp.com/nomad/job-failure-handling/restart 301!
/guides/operating-a-job/failure-handling-strategies/restart.html https://learn.hashicorp.com/nomad/job-failure-handling/restart 301!
/guides/operating-a-job https://learn.hashicorp.com/collections/nomad/manage-jobs 301!
/guides/operating-a-job/index.html https://learn.hashicorp.com/collections/nomad/manage-jobs 301!
/guides/operating-a-job/accessing-logs https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs 301!
/guides/operating-a-job/accessing-logs.html https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs 301!
/guides/operating-a-job/configuring-tasks https://learn.hashicorp.com/tutorials/nomad/jobs-configuring 301!
/guides/operating-a-job/configuring-tasks.html https://learn.hashicorp.com/tutorials/nomad/jobs-configuring 301!
/guides/operating-a-job/external https://learn.hashicorp.com/collections/nomad/plugins 301!
/guides/operating-a-job/external/index.html https://learn.hashicorp.com/collections/nomad/plugins 301!
/guides/operating-a-job/external/lxc https://learn.hashicorp.com/tutorials/nomad/plugin-lxc 301!
/guides/operating-a-job/external/lxc.html https://learn.hashicorp.com/tutorials/nomad/plugin-lxc 301!
/guides/operating-a-job/inspecting-state https://learn.hashicorp.com/tutorials/nomad/jobs-inspec 301!
/guides/operating-a-job/inspecting-state.html https://learn.hashicorp.com/tutorials/nomad/jobs-inspec 301!
/guides/operating-a-job/resource-utilization https://learn.hashicorp.com/tutorials/nomad/jobs-utilization 301!
/guides/operating-a-job/resource-utilization.html https://learn.hashicorp.com/tutorials/nomad/jobs-utilization 301!
/guides/operating-a-job/submitting-jobs https://learn.hashicorp.com/tutorials/nomad/jobs-submit 301!
/guides/operating-a-job/submitting-jobs.html https://learn.hashicorp.com/tutorials/nomad/jobs-submit 301!
/guides/operating-a-job/update-strategies https://learn.hashicorp.com/nomad/update-strategies/ 301!
/guides/operating-a-job/update-strategies/blue-green-and-canary-deployments https://learn.hashicorp.com/nomad/update-strategies/blue-green-and-canary-deployments 301!
/guides/operating-a-job/update-strategies/blue-green-and-canary-deployments.html https://learn.hashicorp.com/nomad/update-strategies/blue-green-and-canary-deployments 301!
/guides/operating-a-job/update-strategies/handling-signals https://learn.hashicorp.com/nomad/update-strategies/handling-signals 301!
/guides/operating-a-job/update-strategies/handling-signals.html https://learn.hashicorp.com/nomad/update-strategies/handling-signals 301!
/guides/operating-a-job/update-strategies/index.html https://learn.hashicorp.com/nomad/update-strategies/ 301!
/guides/operating-a-job/update-strategies/rolling-upgrades https://learn.hashicorp.com/nomad/update-strategies/rolling-upgrades 301!
/guides/operating-a-job/update-strategies/rolling-upgrades.html https://learn.hashicorp.com/nomad/update-strategies/rolling-upgrades 301!
/guides/operating-a-job/advanced-scheduling/advanced-scheduling https://learn.hashicorp.com/collections/nomad/advanced-scheduling 301!
/guides/operating-a-job/advanced-scheduling/advanced-scheduling.html https://learn.hashicorp.com/collections/nomad/advanced-scheduling 301!
/guides/operating-a-job/advanced-scheduling/affinity https://learn.hashicorp.com/tutorials/nomad/affinity 301!
/guides/operating-a-job/advanced-scheduling/affinity.html https://learn.hashicorp.com/tutorials/nomad/affinity 301!
/guides/operating-a-job/advanced-scheduling/preemption-service-batch https://learn.hashicorp.com/tutorials/nomad/preemption 301!
/guides/operating-a-job/advanced-scheduling/preemption-service-batch.html https://learn.hashicorp.com/tutorials/nomad/preemption 301!
/guides/operating-a-job/advanced-scheduling/spread https://learn.hashicorp.com/tutorials/nomad/spread 301!
/guides/operating-a-job/advanced-scheduling/spread.html https://learn.hashicorp.com/tutorials/nomad/spread 301!
/guides/operations https://learn.hashicorp.com/nomad?track=operating-nomad#operations-and-development 301!
/guides/operations/autopilot https://learn.hashicorp.com/nomad/operating-nomad/autopilot 301!
/guides/operations/autopilot.html https://learn.hashicorp.com/nomad/operating-nomad/autopilot 301!
/guides/operations/cluster/automatic https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/operations/cluster/automatic.html https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/operations/cluster/bootstrapping https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/operations/cluster/bootstrapping.html https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/operations/cluster/cloud_auto_join https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/operations/cluster/cloud_auto_join.html https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/operations/cluster/manual https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/operations/cluster/manual.html https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/operations/federation https://learn.hashicorp.com/nomad/operating-nomad/federation 301!
/guides/operations/federation.html https://learn.hashicorp.com/nomad/operating-nomad/federation 301!
/guides/operations https://learn.hashicorp.com/nomad?track=operating-nomad#operations-and-development 301!
/guides/operations/ https://learn.hashicorp.com/nomad?track=operating-nomad#operations-and-development 301!
/guides/operations/index.html https://learn.hashicorp.com/nomad?track=operating-nomad#operations-and-development 301!
/guides/operations/monitoring-and-alerting/monitoring https://learn.hashicorp.com/nomad/operating-nomad/prometheus-metrics 301!
/guides/operations/monitoring-and-alerting/monitoring.html https://learn.hashicorp.com/nomad/operating-nomad/prometheus-metrics 301!
/guides/operations/monitoring-and-alerting/prometheus-metrics https://learn.hashicorp.com/nomad/operating-nomad/prometheus-metrics 301!
/guides/operations/monitoring-and-alerting/prometheus-metrics.html https://learn.hashicorp.com/nomad/operating-nomad/prometheus-metrics 301!
/guides/operations/monitoring/nomad-metrics https://learn.hashicorp.com/nomad/operating-nomad/prometheus-metrics 301!
/guides/operations/monitoring/nomad-metrics.html https://learn.hashicorp.com/nomad/operating-nomad/prometheus-metrics 301!
/guides/operations/node-draining https://learn.hashicorp.com/nomad/operating-nomad/node-draining 301!
/guides/operations/node-draining.html https://learn.hashicorp.com/nomad/operating-nomad/node-draining 301!
/guides/operations/outage https://learn.hashicorp.com/nomad/operating-nomad/outage 301!
/guides/operations/outage.html https://learn.hashicorp.com/nomad/operating-nomad/outage 301!
/guides/operating-a-job/failure-handling-strategies https://learn.hashicorp.com/collections/nomad/job-failure-handling 301!
/guides/operating-a-job/failure-handling-strategies/check-restart https://learn.hashicorp.com/tutorials/nomad/failures-check-restart 301!
/guides/operating-a-job/failure-handling-strategies/check-restart.html https://learn.hashicorp.com/tutorials/nomad/failures-check-restart 301!
/guides/operating-a-job/failure-handling-strategies/index.html https://learn.hashicorp.com/collections/nomad/job-failure-handling 301!
/guides/operating-a-job/failure-handling-strategies/reschedule https://learn.hashicorp.com/tutorials/nomad/failures-reschedule 301!
/guides/operating-a-job/failure-handling-strategies/reschedule.html https://learn.hashicorp.com/tutorials/nomad/failures-reschedule 301!
/guides/operating-a-job/failure-handling-strategies/restart https://learn.hashicorp.com/tutorials/nomad/failures-restart 301!
/guides/operating-a-job/failure-handling-strategies/restart.html https://learn.hashicorp.com/tutorials/nomad/failures-restart 301!
/guides/security https://learn.hashicorp.com/nomad?track=acls#acls 301!
/guides/security/acl https://learn.hashicorp.com/nomad?track=acls#acls 301!
/guides/security/acl.html https://learn.hashicorp.com/nomad?track=acls#acls 301!
/guides/security/encryption https://learn.hashicorp.com/nomad/transport-security/gossip-encryption 301!
/guides/security/encryption.html https://learn.hashicorp.com/nomad/transport-security/gossip-encryption 301!
/guides/security/index.html https://learn.hashicorp.com/nomad?track=acls#acls 301!
/guides/security/securing-nomad https://learn.hashicorp.com/nomad/transport-security/enable-tls 301!
/guides/security/securing-nomad.html https://learn.hashicorp.com/nomad/transport-security/enable-tls 301!
/guides/security/vault-pki-integration https://learn.hashicorp.com/nomad/vault-integration/vault-pki-nomad 301!
/guides/security/vault-pki-integration.html https://learn.hashicorp.com/nomad/vault-integration/vault-pki-nomad 301!
/guides/operating-a-job/update-strategies https://learn.hashicorp.com/tutorials/nomad/job-update-strategies 301!
/guides/operating-a-job/update-strategies/blue-green-and-canary-deployments https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments 301!
/guides/operating-a-job/update-strategies/blue-green-and-canary-deployments.html https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments 301!
/guides/operating-a-job/update-strategies/handling-signals https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals 301!
/guides/operating-a-job/update-strategies/handling-signals.html https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals 301!
/guides/operating-a-job/update-strategies/index.html https://learn.hashicorp.com/tutorials/nomad/job-update-strategies 301!
/guides/operating-a-job/update-strategies/rolling-upgrades https://learn.hashicorp.com/tutorials/nomad/job-rolling-update 301!
/guides/operating-a-job/update-strategies/rolling-upgrades.html https://learn.hashicorp.com/tutorials/nomad/job-rolling-update 301!
/guides/operations https://learn.hashicorp.com/collections/nomad/manage-clusters 301!
/guides/operations/autopilot https://learn.hashicorp.com/tutorials/nomad/autopilot 301!
/guides/operations/autopilot.html https://learn.hashicorp.com/tutorials/nomad/autopilot 301!
/guides/operations/cluster/automatic https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/operations/cluster/automatic.html https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/operations/cluster/bootstrapping https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/operations/cluster/bootstrapping.html https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/operations/cluster/cloud_auto_join https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/operations/cluster/cloud_auto_join.html https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/operations/cluster/manual https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/operations/cluster/manual.html https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/operations/federation https://learn.hashicorp.com/tutorials/nomad/federation 301!
/guides/operations/federation.html https://learn.hashicorp.com/tutorials/nomad/federation 301!
/guides/operations https://learn.hashicorp.com/collections/nomad/manage-clusters 301!
/guides/operations/ https://learn.hashicorp.com/collections/nomad/manage-clusters 301!
/guides/operations/index.html https://learn.hashicorp.com/collections/nomad/manage-clusters 301!
/guides/operations/monitoring-and-alerting/monitoring https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics 301!
/guides/operations/monitoring-and-alerting/monitoring.html https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics 301!
/guides/operations/monitoring-and-alerting/prometheus-metrics https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics 301!
/guides/operations/monitoring-and-alerting/prometheus-metrics.html https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics 301!
/guides/operations/monitoring/nomad-metrics https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics 301!
/guides/operations/monitoring/nomad-metrics.html https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics 301!
/guides/operations/node-draining https://learn.hashicorp.com/tutorials/nomad/node-drain 301!
/guides/operations/node-draining.html https://learn.hashicorp.com/tutorials/nomad/node-drain 301!
/guides/operations/outage https://learn.hashicorp.com/tutorials/nomad/outage-recovery 301!
/guides/operations/outage.html https://learn.hashicorp.com/tutorials/nomad/outage-recovery 301!
/guides/security https://learn.hashicorp.com/collections/nomad/access-control 301!
/guides/security/acl https://learn.hashicorp.com/collections/nomad/access-control 301!
/guides/security/acl.html https://learn.hashicorp.com/collections/nomad/access-control 301!
/guides/security/encryption https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption 301!
/guides/security/encryption.html https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption 301!
/guides/security/index.html https://learn.hashicorp.com/collections/nomad/access-control 301!
/guides/security/securing-nomad https://learn.hashicorp.com/tutorials/nomad/security-enable-tls 301!
/guides/security/securing-nomad.html https://learn.hashicorp.com/tutorials/nomad/security-enable-tls 301!
/guides/security/vault-pki-integration https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad 301!
/guides/security/vault-pki-integration.html https://learn.hashicorp.com/tutorials/nomad/vault-pki-nomad 301!
# Multi-part UI guides
/guides/ui.html https://learn.hashicorp.com/nomad?track=web-ui#web-ui 301!
/guides/ui https://learn.hashicorp.com/nomad?track=web-ui#web-ui 301!
/guides/ui.html https://learn.hashicorp.com/collections/nomad/web-ui 301!
/guides/ui https://learn.hashicorp.com/collections/nomad/web-ui 301!
# Website
@@ -173,18 +171,18 @@
/resources /resources 301!
/docs/agent/config.html /docs/configuration 301!
/docs/agent/config /docs/configuration 301!
/docs/jobops https://learn.hashicorp.com/nomad?track=managing-jobs#managing-jobs 301!
/docs/jobops/index.html https://learn.hashicorp.com/nomad?track=managing-jobs#managing-jobs 301!
/docs/jobops/taskconfig.html https://learn.hashicorp.com/nomad/managing-jobs/configuring-tasks 301!
/docs/jobops/taskconfig https://learn.hashicorp.com/nomad/managing-jobs/configuring-tasks 301!
/docs/jobops/inspecting.html https://learn.hashicorp.com/nomad/managing-jobs/inspecting-state 301!
/docs/jobops/inspecting https://learn.hashicorp.com/nomad/managing-jobs/inspecting-state 301!
/docs/jobops/resources.html https://learn.hashicorp.com/nomad/managing-jobs/resource-utilization 301!
/docs/jobops/resources https://learn.hashicorp.com/nomad/managing-jobs/resource-utilization 301!
/docs/jobops/logs.html https://learn.hashicorp.com/nomad/managing-jobs/accessing-logs 301!
/docs/jobops/logs https://learn.hashicorp.com/nomad/managing-jobs/accessing-logs 301!
/docs/jobops/updating.html https://learn.hashicorp.com/nomad/update-strategies/ 301!
/docs/jobops/updating https://learn.hashicorp.com/nomad/update-strategies/ 301!
/docs/jobops https://learn.hashicorp.com/collections/nomad/manage-jobs 301!
/docs/jobops/index.html https://learn.hashicorp.com/collections/nomad/manage-jobs 301!
/docs/jobops/taskconfig.html https://learn.hashicorp.com/tutorials/nomad/jobs-configuring 301!
/docs/jobops/taskconfig https://learn.hashicorp.com/tutorials/nomad/jobs-configuring 301!
/docs/jobops/inspecting.html https://learn.hashicorp.com/tutorials/nomad/jobs-inspect 301!
/docs/jobops/inspecting https://learn.hashicorp.com/tutorials/nomad/jobs-inspect 301!
/docs/jobops/resources.html https://learn.hashicorp.com/tutorials/nomad/jobs-utilization 301!
/docs/jobops/resources https://learn.hashicorp.com/tutorials/nomad/jobs-utilization 301!
/docs/jobops/logs.html https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs 301!
/docs/jobops/logs https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs 301!
/docs/jobops/updating.html https://learn.hashicorp.com/collections/nomad/job-updates 301!
/docs/jobops/updating https://learn.hashicorp.com/collections/nomad/job-updates 301!
/docs/jobops/servicediscovery.html /docs/integrations/consul-integration 301!
/docs/jobops/servicediscovery /docs/integrations/consul-integration 301!
/docs/jobspec /docs/job-specification 301!
@@ -203,12 +201,12 @@
/docs/jobspec/networking.html /docs/job-specification/network 301!
/docs/jobspec/networking /docs/job-specification/network 301!
/docs/job-specification/index.html /docs/job-specification 301!
/docs/cluster/automatic.html https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/docs/cluster/automatic https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/docs/cluster/manual.html https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/docs/cluster/manual https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/docs/cluster/federation.html https://learn.hashicorp.com/nomad/operating-nomad/federation 301!
/docs/cluster/federation https://learn.hashicorp.com/nomad/operating-nomad/federation 301!
/docs/cluster/automatic.html https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/docs/cluster/automatic https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/docs/cluster/manual.html https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/docs/cluster/manual https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/docs/cluster/federation.html https://learn.hashicorp.com/tutorials/nomad/federation 301!
/docs/cluster/federation https://learn.hashicorp.com/tutorials/nomad/federation 301!
/docs/cluster/requirements.html /docs/install/production/requirements/ 301!
/docs/cluster/requirements /docs/install/production/requirements/ 301!
/docs/commands/operator-index.html /docs/commands/operator 301!
@@ -265,31 +263,31 @@
/docs/drivers/external/podman /docs/drivers/podman 301!
# Moved /docs/operating-a-job/ -> /guides/operating-a-job/
/docs/operating-a-job https://learn.hashicorp.com/nomad?track=managing-jobs#managing-jobs 301!
/docs/operating-a-job/index.html https://learn.hashicorp.com/nomad?track=managing-jobs#managing-jobs 301!
/docs/operating-a-job/accessing-logs.html https://learn.hashicorp.com/nomad/managing-jobs/accessing-logs 301!
/docs/operating-a-job/inspecting-state.html https://learn.hashicorp.com/nomad/managing-jobs/inspecting-state 301!
/docs/operating-a-job/resource-utilization.html https://learn.hashicorp.com/nomad/managing-jobs/resource-utilization 301!
/docs/operating-a-job/configuring-tasks.html https://learn.hashicorp.com/nomad/managing-jobs/configuring-tasks 301!
/docs/operating-a-job/submitting-jobs.html https://learn.hashicorp.com/nomad/managing-jobs/submitting-jobs 301!
/docs/operating-a-job https://learn.hashicorp.com/collections/nomad/manage-jobs 301!
/docs/operating-a-job/index.html https://learn.hashicorp.com/collections/nomad/manage-jobs 301!
/docs/operating-a-job/accessing-logs.html https://learn.hashicorp.com/tutorials/nomad/jobs-accessing-logs 301!
/docs/operating-a-job/inspecting-state.html https://learn.hashicorp.com/tutorials/nomad/jobs-inspect 301!
/docs/operating-a-job/resource-utilization.html https://learn.hashicorp.com/tutorials/nomad/jobs-utilization 301!
/docs/operating-a-job/configuring-tasks.html https://learn.hashicorp.com/tutorials/nomad/jobs-configuring 301!
/docs/operating-a-job/submitting-jobs.html https://learn.hashicorp.com/tutorials/nomad/jobs-submit 301!
/docs/operating-a-job/failure-handling-strategies https://learn.hashicorp.com/nomad/job-failure-handling/failure-handling 301!
/docs/operating-a-job/failure-handling-strategies/index.html https://learn.hashicorp.com/nomad/job-failure-handling/failure-handling 301!
/docs/operating-a-job/failure-handling-strategies/check-restart.html https://learn.hashicorp.com/nomad/job-failure-handling/check-restart 301!
/docs/operating-a-job/failure-handling-strategies/check-restart https://learn.hashicorp.com/nomad/job-failure-handling/check-restart 301!
/docs/operating-a-job/failure-handling-strategies/reschedule.html https://learn.hashicorp.com/nomad/job-failure-handling/reschedule 301!
/docs/operating-a-job/failure-handling-strategies/reschedule https://learn.hashicorp.com/nomad/job-failure-handling/reschedule 301!
/docs/operating-a-job/failure-handling-strategies/restart.html https://learn.hashicorp.com/nomad/job-failure-handling/restart 301!
/docs/operating-a-job/failure-handling-strategies/restart https://learn.hashicorp.com/nomad/job-failure-handling/restart 301!
/docs/operating-a-job/failure-handling-strategies https://learn.hashicorp.com/collections/nomad/job-failure-handling 301!
/docs/operating-a-job/failure-handling-strategies/index.html https://learn.hashicorp.com/collections/nomad/job-failure-handling 301!
/docs/operating-a-job/failure-handling-strategies/check-restart.html https://learn.hashicorp.com/tutorials/nomad/failures-check-restart 301!
/docs/operating-a-job/failure-handling-strategies/check-restart https://learn.hashicorp.com/tutorials/nomad/failures-check-restart 301!
/docs/operating-a-job/failure-handling-strategies/reschedule.html https://learn.hashicorp.com/tutorials/nomad/failures-reschedule 301!
/docs/operating-a-job/failure-handling-strategies/reschedule https://learn.hashicorp.com/tutorials/nomad/failures-reschedule 301!
/docs/operating-a-job/failure-handling-strategies/restart.html https://learn.hashicorp.com/tutorials/nomad/failures-restart 301!
/docs/operating-a-job/failure-handling-strategies/restart https://learn.hashicorp.com/tutorials/nomad/failures-restart 301!
/docs/operating-a-job/update-strategies https://learn.hashicorp.com/nomad/update-strategies/ 301!
/docs/operating-a-job/update-strategies/index.html https://learn.hashicorp.com/nomad/update-strategies/ 301!
/docs/operating-a-job/update-strategies/blue-green-and-canary-deployments.html https://learn.hashicorp.com/nomad/update-strategies/blue-green-and-canary-deployments 301!
/docs/operating-a-job/update-strategies/blue-green-and-canary-deployments https://learn.hashicorp.com/nomad/update-strategies/blue-green-and-canary-deployments 301!
/docs/operating-a-job/update-strategies/handling-signals.html https://learn.hashicorp.com/nomad/update-strategies/handling-signals 301!
/docs/operating-a-job/update-strategies/handling-signals https://learn.hashicorp.com/nomad/update-strategies/handling-signals 301!
/docs/operating-a-job/update-strategies/rolling-upgrades.html https://learn.hashicorp.com/nomad/update-strategies/rolling-upgrades 301!
/docs/operating-a-job/update-strategies/rolling-upgrades https://learn.hashicorp.com/nomad/update-strategies/rolling-upgrades 301!
/docs/operating-a-job/update-strategies https://learn.hashicorp.com/collections/nomad/job-updates 301!
/docs/operating-a-job/update-strategies/index.html https://learn.hashicorp.com/collections/nomad/job-updates 301!
/docs/operating-a-job/update-strategies/blue-green-and-canary-deployments.html https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments 301!
/docs/operating-a-job/update-strategies/blue-green-and-canary-deployments https://learn.hashicorp.com/tutorials/nomad/job-blue-green-and-canary-deployments 301!
/docs/operating-a-job/update-strategies/handling-signals.html https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals 301!
/docs/operating-a-job/update-strategies/handling-signals https://learn.hashicorp.com/tutorials/nomad/job-update-handle-signals 301!
/docs/operating-a-job/update-strategies/rolling-upgrades.html https://learn.hashicorp.com/tutorials/nomad/job-rolling-update 301!
/docs/operating-a-job/update-strategies/rolling-upgrades https://learn.hashicorp.com/tutorials/nomad/job-rolling-update 301!
# Moved /docs/agent/configuration/ -> /docs/configuration/ 301!
@@ -320,12 +318,12 @@
# Moved guide-like docs to /guides
/docs/agent /docs/install/production/nomad-agent/ 301!
/docs/agent/index.html /docs/install/production/nomad-agent/ 301!
/docs/agent/cloud_auto_join.html https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/docs/agent/cloud_auto_join https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/docs/agent/telemetry.html https://learn.hashicorp.com/nomad/operating-nomad/prometheus-metrics 301!
/docs/agent/telemetry https://learn.hashicorp.com/nomad/operating-nomad/prometheus-metrics 301!
/docs/agent/encryption.html https://learn.hashicorp.com/nomad/transport-security/gossip-encryption 301!
/docs/agent/encryption https://learn.hashicorp.com/nomad/transport-security/gossip-encryption 301!
/docs/agent/cloud_auto_join.html https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/docs/agent/cloud_auto_join https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/docs/agent/telemetry.html https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics 301!
/docs/agent/telemetry https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics 301!
/docs/agent/encryption.html https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption 301!
/docs/agent/encryption https://learn.hashicorp.com/tutorials/nomad/security-gossip-encryption 301!
/docs/service-discovery /docs/integrations/consul-integration 301!
/docs/service-discovery/index.html /docs/integrations/consul-integration 301!
@@ -383,53 +381,44 @@
# Guides
# Reorganized Guides by Persona
/guides/autopilot.html https://learn.hashicorp.com/nomad/operating-nomad/autopilot 301!
/guides/autopilot https://learn.hashicorp.com/nomad/operating-nomad/autopilot 301!
/guides/cluster/automatic.html https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/cluster/automatic https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/cluster/bootstrapping.html https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/cluster/bootstrapping https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/operations/cluster/bootstrapping.html https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/operations/cluster/bootstrapping https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/cluster/manual.html https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/cluster/manual https://learn.hashicorp.com/nomad/operating-nomad/clustering 301!
/guides/cluster/federation https://learn.hashicorp.com/nomad/operating-nomad/federation 301!
/guides/autopilot.html https://learn.hashicorp.com/tutorials/nomad/autopilot 301!
/guides/autopilot https://learn.hashicorp.com/tutorials/nomad/autopilot 301!
/guides/cluster/automatic.html https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/cluster/automatic https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/cluster/bootstrapping.html https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/cluster/bootstrapping https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/operations/cluster/bootstrapping.html https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/operations/cluster/bootstrapping https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/cluster/manual.html https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/cluster/manual https://learn.hashicorp.com/tutorials/nomad/clustering 301!
/guides/cluster/federation https://learn.hashicorp.com/tutorials/nomad/federation 301!
/guides/cluster/requirements /docs/install/production/requirements 301!
/guides/nomad-metrics.html https://learn.hashicorp.com/nomad/operating-nomad/prometheus-metrics 301!
/guides/nomad-metrics https://learn.hashicorp.com/nomad/operating-nomad/prometheus-metrics 301!
/guides/node-draining.html https://learn.hashicorp.com/nomad/operating-nomad/node-draining 301!
/guides/node-draining https://learn.hashicorp.com/nomad/operating-nomad/node-draining 301!
/guides/outage.html https://learn.hashicorp.com/nomad/operating-nomad/outage 301!
/guides/outage https://learn.hashicorp.com/nomad/operating-nomad/outage 301!
/guides/acl.html https://learn.hashicorp.com/nomad?track=acls#acls 301!
/guides/acl https://learn.hashicorp.com/nomad?track=acls#acls 301!
/guides/namespaces.html https://learn.hashicorp.com/nomad/governance-and-policy/namespaces 301!
/guides/namespaces https://learn.hashicorp.com/nomad/governance-and-policy/namespaces 301!
/guides/quotas.html https://learn.hashicorp.com/nomad/governance-and-policy/quotas 301!
/guides/quotas https://learn.hashicorp.com/nomad/governance-and-policy/quotas 301!
/guides/securing-nomad.html https://learn.hashicorp.com/nomad/transport-security/enable-tls 301!
/guides/securing-nomad https://learn.hashicorp.com/nomad/transport-security/enable-tls 301!
/guides/sentinel-policy.html https://learn.hashicorp.com/nomad/governance-and-policy/sentinel 301!
/guides/sentinel-policy https://learn.hashicorp.com/nomad/governance-and-policy/sentinel 301!
/guides/sentinel/job.html https://learn.hashicorp.com/nomad/governance-and-policy/sentinel 301!
/guides/sentinel/job https://learn.hashicorp.com/nomad/governance-and-policy/sentinel 301!
/guides/nomad-metrics.html https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics 301!
/guides/nomad-metrics https://learn.hashicorp.com/tutorials/nomad/prometheus-metrics 301!
/guides/node-draining.html https://learn.hashicorp.com/tutorials/nomad/node-drain 301!
/guides/node-draining https://learn.hashicorp.com/tutorials/nomad/node-drain 301!
/guides/outage https://learn.hashicorp.com/tutorials/nomad/outage-recovery 301!
/guides/acl.html https://learn.hashicorp.com/collections/nomad/access-control 301!
/guides/acl https://learn.hashicorp.com/collections/nomad/access-control 301!
/guides/namespaces.html https://learn.hashicorp.com/tutorials/nomad/namespaces 301!
/guides/namespaces https://learn.hashicorp.com/tutorials/nomad/namespaces 301!
/guides/quotas.html https://learn.hashicorp.com/tutorials/nomad/quotas 301!
/guides/quotas https://learn.hashicorp.com/tutorials/nomad/quotas 301!
/guides/securing-nomad.html https://learn.hashicorp.com/tutorials/nomad/security-enable-tls 301!
/guides/securing-nomad https://learn.hashicorp.com/tutorials/nomad/security-enable-tls 301!
/guides/sentinel-policy.html https://learn.hashicorp.com/tutorials/nomad/sentinel 301!
/guides/sentinel-policy https://learn.hashicorp.com/tutorials/nomad/sentinel 301!
/guides/sentinel/job.html https://learn.hashicorp.com/tutorials/nomad/sentinel 301!
/guides/sentinel/job https://learn.hashicorp.com/tutorials/nomad/sentinel 301!
/guides/analytical-workloads/spark/spark.html https://learn.hashicorp.com/nomad?track=spark#spark 301!
/guides/analytical-workloads/spark/spark https://learn.hashicorp.com/nomad?track=spark#spark 301!
/guides/spark https://learn.hashicorp.com/nomad?track=spark#spark 301!
/guides/spark/index.html https://learn.hashicorp.com/nomad?track=spark#spark 301!
/guides/spark/spark.html https://learn.hashicorp.com/nomad?track=spark#spark 301!
/guides/spark/spark https://learn.hashicorp.com/nomad?track=spark#spark 301!
/guides/spark/pre.html https://learn.hashicorp.com/nomad/spark/pre 301!
/guides/spark/pre https://learn.hashicorp.com/nomad/spark/pre 301!
/guides/security/namespaces.html https://learn.hashicorp.com/nomad/governance-and-policy/namespaces 301!
/guides/security/namespaces https://learn.hashicorp.com/nomad/governance-and-policy/namespaces 301!
/guides/security/quotas.html https://learn.hashicorp.com/nomad/governance-and-policy/quotas 301!
/guides/security/quotas https://learn.hashicorp.com/nomad/governance-and-policy/quotas 301!
/guides/security/sentinel/job.html https://learn.hashicorp.com/nomad/governance-and-policy/quotas 301!
/guides/security/sentinel/job https://learn.hashicorp.com/nomad/governance-and-policy/quotas 301!
/guides/security/sentinel-policy.html https://learn.hashicorp.com/nomad/governance-and-policy/sentinel 301!
/guides/security/sentinel-policy https://learn.hashicorp.com/nomad/governance-and-policy/sentinel 301!
/guides/security/namespaces.html https://learn.hashicorp.com/tutorials/nomad/namespaces 301!
/guides/security/namespaces https://learn.hashicorp.com/tutorials/nomad/namespaces 301!
/guides/security/quotas.html https://learn.hashicorp.com/tutorials/nomad/quotas 301!
/guides/security/quotas https://learn.hashicorp.com/tutorials/nomad/quotas 301!
/guides/security/sentinel/job.html https://learn.hashicorp.com/tutorials/nomad/quotas 301!
/guides/security/sentinel/job https://learn.hashicorp.com/tutorials/nomad/quotas 301!
/guides/security/sentinel-policy.html https://learn.hashicorp.com/tutorials/nomad/sentinel 301!
/guides/security/sentinel-policy https://learn.hashicorp.com/tutorials/nomad/sentinel 301!
/guides/operations/install/index.html /docs/install 301!
/guides/operations/install/index /docs/install 301!
/guides/operations/agent/index.html /docs/install/production/nomad-agent 301!
@@ -437,11 +426,11 @@
/guides/operations/requirements /docs/install/production/requirements 301!
/guides/operations/consul-integration/index.html /docs/integrations/consul-integration 301!
/guides/operations/vault-integration/index.html /docs/integrations/vault-integration 301!
/guides/advanced-scheduling/ https://learn.hashicorp.com/nomad/advanced-scheduling/advanced-scheduling 301!
/guides/external https://learn.hashicorp.com/nomad?track=using-plugins#using-plugins 301!
/guides/external/index.html https://learn.hashicorp.com/nomad?track=spark#spark 301!
/guides/external/lxc.html https://learn.hashicorp.com/nomad/using-plugins/lxc 301!
/guides/external/lxc https://learn.hashicorp.com/nomad/using-plugins/lxc 301!
/guides/advanced-scheduling/ https://learn.hashicorp.com/collections/nomad/advanced-scheduling 301!
/guides/external https://learn.hashicorp.com/collections/nomad/plugins 301!
/guides/external/index.html https://learn.hashicorp.com/collections/nomad/plugins 301!
/guides/external/lxc.html https://learn.hashicorp.com/tutorials/nomad/plugin-lxc 301!
/guides/external/lxc https://learn.hashicorp.com/tutorials/nomad/plugin-lxc 301!
/guides/operations/upgrade /docs/upgrade 301!
/guides/operations/upgrade/index.html /docs/upgrade 301!
/guides/operations/upgrade/upgrade-specific.html /docs/upgrade/upgrade-specific 301!

2
website/pages/api-docs/acl-policies.mdx
View File

@@ -8,7 +8,7 @@ description: The /acl/policy endpoints are used to configure and manage ACL poli
# 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).
For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
## List Policies

4
website/pages/api-docs/acl-tokens.mdx
View File

@@ -8,13 +8,13 @@ description: The /acl/token/ endpoints are used to configure and manage ACL toke
# 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).
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/nomad?track=acls#acls) is performed.
until a [bootstrap reset](https://learn.hashicorp.com/tutorials/nomad/access-control-bootstrap#re-bootstrap-acl-system) is performed.
| Method | Path | Produces |
| ------ | ---------------- | ------------------ |

4
website/pages/api-docs/index.mdx
View File

@@ -24,7 +24,7 @@ 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 & Ports
## 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
@@ -76,7 +76,7 @@ administration.
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).
For more details about ACLs, please see the [ACL Guide](https://learn.hashicorp.com/collections/nomad/access-control).
## Authentication

2
website/pages/api-docs/nodes.mdx
View File

@@ -841,7 +841,7 @@ $ curl \
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.
Guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for suggested usage.
| Method | Path | Produces |
| ------ | ------------------------- | ------------------ |

2
website/pages/api-docs/operator.mdx
View File

@@ -15,7 +15,7 @@ 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
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.

4
website/pages/api-docs/sentinel-policies.mdx
View File

@@ -10,9 +10,9 @@ description: >-
# 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).
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/nomad?track=acls#operations-and-development).
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).
~> **Enterprise Only!** This API endpoint and functionality only exists in
Nomad Enterprise. This is not present in the open source version of Nomad.

4
website/pages/docs/autoscaling/agent.mdx
View File

@@ -389,8 +389,8 @@ strategy "example-strategy-plugin" {
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
[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

6
website/pages/docs/autoscaling/plugins/target.mdx
View File

@@ -148,12 +148,12 @@ check {
- `node_purge` `(bool: "false")` A boolean flag to determine whether Nomad clients should
be [purged][nomad_node_purge] when performing scale in 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_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]: https://www.nomadproject.io/api/nodes.html#purge-node
[nomad_node_purge]: /api-docs/nodes#purge-node

2
website/pages/docs/commands/acl/index.mdx
View File

@@ -42,4 +42,4 @@ subcommands are available:
[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
[secure-guide]: https://learn.hashicorp.com/collections/nomad/access-control

32
website/pages/docs/commands/agent.mdx
View File

@@ -182,11 +182,11 @@ via CLI arguments. The `agent` command accepts the following arguments:
Vault over TLS.
[address]: /docs/configuration/consul#address
[alloc_dir]: /docs/configuration/client/#alloc_dir
[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
[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
@@ -195,31 +195,31 @@ via CLI arguments. The `agent` command accepts the following arguments:
[client_service_name]: /docs/configuration/consul#client_service_name
[configuration]: /docs/configuration
[data_dir]: /docs/configuration#data_dir
[datacenter]: /docs/configuration/#datacenter
[datacenter]: /docs/configuration#datacenter
[enabled]: /docs/configuration/acl#enabled
[encryption overview]: https://learn.hashicorp.com/nomad/transport-security/gossip-encryption
[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
[network_speed]: /docs/configuration/client/#network_speed
[node_class]: /docs/configuration/client/#node_class
[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
[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
[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
[servers]: /docs/configuration/client#servers
[ssl]: /docs/configuration/consul#ssl
[state_dir]: /docs/configuration/client/#state_dir
[state_dir]: /docs/configuration/client#state_dir
[token]: /docs/configuration/consul#token
[verify_ssl]: /docs/configuration/consul#verify_ssl

2
website/pages/docs/commands/deployment/unblock.mdx
View File

@@ -70,4 +70,4 @@ cache 3 2 1 0
```
[eval status]: /docs/commands/eval-status
[federated regions]: https://learn.hashicorp.com/nomad/operating-nomad/federation
[federated regions]: https://learn.hashicorp.com/tutorials/nomad/federation

2
website/pages/docs/commands/node/drain.mdx
View File

@@ -138,5 +138,5 @@ $ 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
[workload migration guide]: https://learn.hashicorp.com/tutorials/nomad/node-drain
[internals-csi]: /docs/internals/plugins/csi

2
website/pages/docs/commands/operator/autopilot-get-config.mdx
View File

@@ -63,4 +63,4 @@ UpgradeMigrationTag = ""
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
[autopilot guide]: https://learn.hashicorp.com/tutorials/nomad/autopilot

2
website/pages/docs/commands/operator/autopilot-set-config.mdx
View File

@@ -60,4 +60,4 @@ 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
[autopilot guide]: https://learn.hashicorp.com/tutorials/nomad/autopilot

2
website/pages/docs/commands/operator/index.mdx
View File

@@ -56,7 +56,7 @@ The following subcommands are available:
[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
[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'

2
website/pages/docs/commands/operator/raft-list-peers.mdx
View File

@@ -59,4 +59,4 @@ nomad-server03.global 10.10.11.7:4647 10.10.11.7:4647 follower true
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
[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery

2
website/pages/docs/commands/operator/raft-remove-peer.mdx
View File

@@ -42,4 +42,4 @@ nomad operator raft remove-peer [options]
[`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
[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery

2
website/pages/docs/commands/operator/snapshot-inspect.mdx
View File

@@ -27,4 +27,4 @@ Version 1
nomad operator snapshot inspect <file>
```
[outage recovery]: https://learn.hashicorp.com/nomad/operating-nomad/outage
[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery

2
website/pages/docs/commands/operator/snapshot-restore.mdx
View File

@@ -35,4 +35,4 @@ nomad operator snapshot restore [options] <file>
@include 'general_options.mdx'
[outage recovery]: https://learn.hashicorp.com/nomad/operating-nomad/outage
[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery

2
website/pages/docs/commands/operator/snapshot-save.mdx
View File

@@ -45,4 +45,4 @@ nomad operator snapshot save [options] <file>
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
[outage recovery]: https://learn.hashicorp.com/tutorials/nomad/outage-recovery

2
website/pages/docs/configuration/acl.mdx
View File

@@ -44,4 +44,4 @@ acl {
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
[secure-guide]: https://learn.hashicorp.com/collections/nomad/access-control

2
website/pages/docs/configuration/autopilot.mdx
View File

@@ -12,7 +12,7 @@ description: >-
<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).
For more information about Autopilot, see the [Autopilot Guide](https://learn.hashicorp.com/tutorials/nomad/autopilot).
```hcl
autopilot {

2
website/pages/docs/configuration/consul.mdx
View File

@@ -177,4 +177,4 @@ consul {
```
[consul]: https://www.consul.io/ 'Consul by HashiCorp'
[bootstrap]: https://learn.hashicorp.com/nomad/operating-nomad/clustering 'Automatic Bootstrapping'
[bootstrap]: https://learn.hashicorp.com/tutorials/nomad/clustering 'Automatic Bootstrapping'

12
website/pages/docs/configuration/server.mdx
View File

@@ -162,7 +162,7 @@ server {
- `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).
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,
@@ -177,7 +177,7 @@ server {
- `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).
For more information, see the [Autopilot Guide](https://learn.hashicorp.com/tutorials/nomad/autopilot).
### Deprecated Parameters
@@ -243,7 +243,7 @@ server {
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).
[automatic Nomad bootstrapping documentation](https://learn.hashicorp.com/tutorials/nomad/clustering).
### Restricting Schedulers
@@ -266,8 +266,8 @@ 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 [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
@@ -291,7 +291,7 @@ server {
}
```
[encryption]: https://learn.hashicorp.com/nomad/transport-security/gossip-encryption 'Nomad Encryption Overview'
[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

2
website/pages/docs/configuration/server_join.mdx
View File

@@ -119,7 +119,7 @@ nomad-01.company.local => nomad-01.company.local:4648
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.
Auto-join](#cloud-auto-join) for more information.
```
"provider=aws tag_key=..." => 1.2.3.4:4648

2
website/pages/docs/configuration/tls.mdx
View File

@@ -26,7 +26,7 @@ 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).
the [Enable TLS Encryption for Nomad Tutorial](https://learn.hashicorp.com/tutorials/nomad/security-enable-tls).
## `tls` Parameters

6
website/pages/docs/configuration/vault.mdx
View File

@@ -61,16 +61,16 @@ vault {
- `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)
[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/#inlinecode-tls_require_and_verify_client_cert)
[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/index.html)
- `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.

2
website/pages/docs/drivers/external/lxc.mdx vendored
View File

@@ -181,7 +181,7 @@ 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-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

2
website/pages/docs/drivers/index.mdx
View File

@@ -39,4 +39,4 @@ 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
[acl_guide]: https://learn.hashicorp.com/collections/nomad/access-control

18
website/pages/docs/enterprise.mdx
View File

@@ -32,7 +32,7 @@ Nomad Enterprise Platform enables operators to easily upgrade Nomad as well as e
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.
See the [Autopilot - Upgrade Migrations](https://learn.hashicorp.com/tutorials/nomad/autopilot#upgrade-migrations) documentation for a thorough overview.
### Automated Backups
@@ -40,25 +40,25 @@ Automated Backups allows operators to run the snapshot agent as a long-running d
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.
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/nomad/operating-nomad/autopilot#server-read-and-scheduling-scaling) documentation for a thorough overview.
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/nomad/operating-nomad/autopilot#redundancy-zones) documentation for a thorough overview.
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](https://www.nomadproject.io/docs/integrations/vault-integration#enterprise-configuration) for more information.
See the [Vault Integration documentation](/docs/integrations/vault-integration#enterprise-configuration) for more information.
## Governance & Policy
@@ -78,7 +78,7 @@ Namespaces enable multiple teams to safely use a shared multi-region Nomad envir
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.
See the [Namespaces Guide](https://learn.hashicorp.com/tutorials/nomad/namespaces) for a thorough overview.
### Resource Quotas
@@ -86,18 +86,18 @@ Resource Quotas enable an operator to limit resource consumption across teams or
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.
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/nomad/governance-and-policy/sentinel) for a thorough overview.
See the [Sentinel Policies Guide](https://learn.hashicorp.com/tutorials/nomad/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.
See the individual Nomad CLI command documentation (e.g., [alloc exec](/docs/commands/alloc/exec#namespace)) for more information.
## Multi-Cluster & Efficiency

4
website/pages/docs/faq.mdx
View File

@@ -58,8 +58,8 @@ 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
[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

6
website/pages/docs/install/index.mdx
View File

@@ -16,7 +16,7 @@ operating systems. You can also [build Nomad from source](#from-source).
<Tabs>
<Tab heading="Manual installation">
You can download a [precompiled binary](https://nomadproject.io/downloads/) and
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
@@ -256,7 +256,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.html
[destroy]: https://www.vagrantup.com/docs/cli/destroy.html
[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'

4
website/pages/docs/install/quickstart.mdx
View File

@@ -100,6 +100,6 @@ 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
[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/

4
website/pages/docs/integrations/consul-connect.mdx
View File

@@ -32,14 +32,14 @@ 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
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/nomad/consul-integration/nomad-connect-acl)
[Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/tutorials/nomad/consul-service-mesh)
guide.
# Nomad Consul Connect Example

2
website/pages/docs/integrations/consul-integration.mdx
View File

@@ -29,7 +29,7 @@ configuration.
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.
Consul](https://learn.hashicorp.com/tutorials/nomad/clustering) guide for more information.
## Service Discovery

26
website/pages/docs/internals/security.mdx
View File

@@ -18,7 +18,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/internals/security.html), which provides
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).
@@ -38,12 +38,12 @@ but the general mechanisms for a secure Nomad deployment revolve around:
authorization for authenticated connections by granting capabilities to ACL
tokens.
* **[Namespaces](/docs/enterprise/index.html#namespaces)**
* **[Namespaces](https://learn.hashicorp.com/tutorials/nomad/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)**
* **[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.
@@ -53,7 +53,7 @@ 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
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).
@@ -110,7 +110,7 @@ recommendations accordingly.
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).
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
@@ -167,9 +167,9 @@ environment.
frequently is highly recommended to reduce damage of accidentally leaked
credentials.
* Use [Vault](/docs/vault-integration/index.html) to create and manage
* 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/index.html) itself
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.
@@ -200,9 +200,9 @@ environment.
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)**
**[`security_opt`](/docs/drivers/docker#security_opt)**
parameter available in the default [Docker
driver](/docs/drivers/docker.html).
driver](/docs/drivers/docker).
* **[Service Mesh](https://www.hashicorp.com/resources/service-mesh-microservices-networking)** -
Integrating service mesh technologies such as
@@ -266,7 +266,7 @@ The following are not part of the threat model for client agents:
* **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).
[`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
@@ -298,7 +298,7 @@ The following are not part of the threat model for client agents:
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)
to an exposed Docker daemon API through other means such as the [`raw_exec`](/docs/drivers/raw_exec)
driver.
@@ -321,6 +321,6 @@ There are two main components to consider to for external threats in a Nomad clu
| **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. |
| **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.html) protocol to manage server membership using [Serf](https://www.serf.io/). |
| **4648** / TCP + UDP | Servers | [gossip](/docs/internals/gossip) protocol to manage server membership using [Serf](https://www.serf.io/). |

4
website/pages/docs/job-specification/connect.mdx
View File

@@ -13,7 +13,7 @@ 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)
the [Secure Nomad Jobs with Consul Connect](https://learn.hashicorp.com/tutorials/nomad/consul-service-mesh)
guide.
```hcl
@@ -199,5 +199,5 @@ service {
[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
[native]: https://www.consul.io/docs/connect/native
[service_task]: /docs/job-specification/service#task-1 'Nomad service task'

2
website/pages/docs/job-specification/csi_plugin.mdx
View File

@@ -100,4 +100,4 @@ job "plugin-efs" {
[csi]: https://github.com/container-storage-interface/spec
[csi_volumes]: /docs/job-specification/volume
[system]: /docs/schedulers/#system
[system]: /docs/schedulers#system

66
website/pages/docs/job-specification/expose.mdx
View File

@@ -21,18 +21,18 @@ description: |-
]}
/>
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` 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](https://www.consul.io/docs/connect/registration/service-registration.html#expose-paths-configuration-reference).
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](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.
Service [check][] configurations can use their [expose][] parameter to
automatically generate expose path configurations for HTTP and gRPC checks.
```hcl
job "expose-check-example" {
@@ -73,9 +73,9 @@ job "expose-check-example" {
```
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.
`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" {
@@ -134,30 +134,34 @@ job "expose-example" {
## `expose` Parameters
- `path` <code>([Path]: nil)</code> - A list of [Envoy Expose Path Configurations](/docs/job-specification/expose/#path-1)
- `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](/docs/job-specification/network#to)
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](https://nomadproject.io/docs/configuration/client/#network_interface)
of the node on the allocated `metrics` [Port](/docs/job-specification/network#port-parameters).
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 {
@@ -183,8 +187,9 @@ service {
## `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.
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 {
@@ -207,11 +212,11 @@ proxy {
### 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.
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 {
@@ -224,5 +229,12 @@ 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
[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

2
website/pages/docs/job-specification/gateway.mdx
View File

@@ -198,7 +198,7 @@ are enabled.
[proxy]: /docs/job-specification/gateway#proxy-parameters
[ingress]: /docs/job-specification/gateway#ingress-parameters
[tls]: /docs/job-specification/gateway#tlsconfig-parameters
[tls]: /docs/job-specification/gateway#tls-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

4
website/pages/docs/job-specification/job.mdx
View File

@@ -244,10 +244,10 @@ $ VAULT_TOKEN="..." nomad job run example.nomad
[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
[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/nomad/operating-nomad/federation
[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'

2
website/pages/docs/job-specification/lifecycle.mdx
View File

@@ -67,4 +67,4 @@ job "docs" {
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
[learn-taskdeps]: https://learn.hashicorp.com/collections/nomad/task-deps

2
website/pages/docs/job-specification/migrate.mdx
View File

@@ -44,7 +44,7 @@ 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
See the [Workload Migration Guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for details
on node draining.
## `migrate` Parameters

4
website/pages/docs/job-specification/multiregion.mdx
View File

@@ -264,9 +264,9 @@ group "worker" {
}
```
[federated regions]: https://learn.hashicorp.com/nomad/operating-nomad/federation
[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/nomad?track=update-strategies#update-strategies
[upgrade strategies]: https://learn.hashicorp.com/collections/nomad/job-updates
[`nomad deployment unblock`]: /docs/commands/deployment/unblock

4
website/pages/docs/job-specification/proxy.mdx
View File

@@ -59,11 +59,11 @@ job "countdash" {
- `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)
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.html#dynamic-configuration)
documentation](https://www.consul.io/docs/connect/proxies/envoy#dynamic-configuration)
for details.
## `proxy` Examples

2
website/pages/docs/job-specification/scaling.mdx
View File

@@ -52,4 +52,4 @@ job "example" {
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'
[count]: /docs/job-specification/group#count 'Nomad Task Group specification'

6
website/pages/docs/job-specification/service.mdx
View File

@@ -126,7 +126,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/internals/anti-entropy.html#enable-tag-override)
[documentation](https://www.consul.io/docs/internals/anti-entropy#enable-tag-override)
for more information.
- `address_mode` `(string: "auto")` - Specifies what address (host or
@@ -702,8 +702,8 @@ advertise and check directly since Nomad isn't managing any port assignments.
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
[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'

8
website/pages/docs/job-specification/update.mdx
View File

@@ -13,7 +13,7 @@ description: |-
<Placement
groups={[
['job', 'update'],
['job', 'group', 'update']
['job', 'group', 'update'],
]}
/>
@@ -266,7 +266,7 @@ group "two" {
}
```
[canary]: https://learn.hashicorp.com/nomad/update-strategies/blue-green-and-canary-deployments 'Nomad Canary Deployments'
[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/nomad/update-strategies/rolling-upgrades 'Nomad Rolling Upgrades'
[strategies]: https://learn.hashicorp.com/nomad/update-strategies 'Nomad Update Strategies'
[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'

2
website/pages/docs/job-specification/volume.mdx
View File

@@ -56,6 +56,6 @@ the [volume_mount][volume_mount] stanza in the `task` configuration.
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
[host_volume]: /docs/configuration/client#host_volume-stanza
[csi_volume]: /docs/commands/volume/register
[csi_plugin]: /docs/job-specification/csi_plugin

2
website/pages/docs/upgrade/index.mdx
View File

@@ -126,7 +126,7 @@ Use the same actions in step #2 above to confirm cluster health.
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
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!

33
website/pages/docs/upgrade/upgrade-specific.mdx
View File

@@ -35,18 +35,17 @@ detailing the missing capability.
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.
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.
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
@@ -107,10 +106,10 @@ 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
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*
Feasability (whether a node is capable of running a job at all) is _not_
affected.
### Periodic Jobs and Daylight Saving Time
@@ -358,14 +357,12 @@ 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,
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
[`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.
@@ -408,18 +405,18 @@ Raft Protocol versions supported by each Nomad version:
</tbody>
</table>
In order to enable all [Autopilot](https://learn.hashicorp.com/nomad/operating-nomad/autopilot) features, all servers
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/nomad/operating-nomad/outage#manual-recovery-using-peersjson) for a description of the required format.
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/nomad/operating-nomad/outage#manual-recovery-using-peersjson) to map the server to its node ID in the Raft quorum configuration.
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
@@ -434,7 +431,7 @@ 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.
guide](https://learn.hashicorp.com/tutorials/nomad/node-drain) for details.
### Periods in Environment Variable Names No Longer Escaped
@@ -609,8 +606,8 @@ deleted and then Nomad 0.3.0 can be launched.
[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
[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

6
website/pages/home/index.jsx
View File

@@ -350,16 +350,14 @@ export default function Homepage() {
title: 'Getting Started',
category: 'Step-by-Step Guides',
time: '24 mins',
link:
'https://learn.hashicorp.com/nomad?track=getting-started#getting-started',
link: 'https://learn.hashicorp.com/collections/nomad/get-started',
image: require('./img/learn-nomad/cap.svg'),
},
{
title: 'Deploy and Manage Nomad Jobs',
category: 'Step-by-Step Guides',
time: '36 mins',
link:
'https://learn.hashicorp.com/nomad?track=managing-jobs#getting-started',
link: 'https://learn.hashicorp.com/collections/nomad/manage-jobs',
image: require('./img/learn-nomad/cubes.svg'),
},
]}

14
website/pages/intro/getting-started/index.mdx
View File

@@ -7,10 +7,10 @@ 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).
To simplify the getting started experience, you can download the precompiled
binary and run it directly (see the instructions for installing Nomad
[here][nomad-install]) or you can optionally work in a Vagrant environment
(detailed in the following section).
## Vagrant Setup (Optional)
@@ -86,6 +86,6 @@ re-create it.
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/
[nomad-install]: /docs/install#installing-nomad
[destroy]: https://www.vagrantup.com/docs/cli/destroy
[install-instructions]: https://www.vagrantup.com/docs/installation

8
website/pages/intro/getting-started/next-steps.mdx
View File

@@ -16,17 +16,17 @@ 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
- [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
- [Job Lifecycle](https://learn.hashicorp.com/collections/nomad/manage-jobs) - 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.
- [Creating a Cluster](https://learn.hashicorp.com/tutorials/nomad/clustering) - Additional
details on joining nodes to create a multi-node Nomad Cluster.
- [Example Terraform configuration](https://github.com/hashicorp/nomad/tree/master/terraform) -
Use Terraform to automatically provision a cluster in AWS.

2
website/pages/use-cases/automated-service-networking-with-consul.jsx
View File

@@ -18,7 +18,7 @@ export default function AutomatedServiceNetworkingWithConsulPage() {
{
text: 'Read More',
url:
'https://learn.hashicorp.com/nomad/operating-nomad/clustering#use-consul-to-automatically-cluster-nodes',
'https://learn.hashicorp.com/tutorials/nomad/clustering#use-consul-to-automatically-cluster-nodes',
type: 'outbound',
},
],

2
website/pages/use-cases/non-containerized-application-orchestration.jsx
View File

@@ -51,7 +51,7 @@ export default function NonContainerizedApplicationOrchestrationPage() {
links: [
{
text: 'Read more',
url: 'https://learn.hashicorp.com/nomad/update-strategies',
url: 'https://learn.hashicorp.com/collections/nomad/job-updates',
type: 'outbound',
},
],

8
website/pages/use-cases/simple-container-orchestration.jsx
View File

@@ -18,8 +18,7 @@ export default function SimpleContainerOrchestrationPage() {
links: [
{
text: 'Read More',
url:
'https://learn.hashicorp.com/nomad?track=managing-jobs#managing-jobs',
url: 'https://learn.hashicorp.com/collections/nomad/manage-jobs',
type: 'outbound',
},
],
@@ -92,8 +91,7 @@ SERVICE_NAME: Nomad
links: [
{
text: 'Read more',
url:
'https://learn.hashicorp.com/nomad/operating-nomad/federation',
url: 'https://learn.hashicorp.com/tutorials/nomad/federation',
type: 'outbound',
},
],
@@ -128,7 +126,7 @@ SERVICE_NAME: Nomad
links: [
{
text: 'Read more',
url: 'https://learn.hashicorp.com/nomad/update-strategies',
url: 'https://learn.hashicorp.com/collections/nomad/job-updates',
type: 'outbound',
},
],