mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
Update rel notes, upgrade links to point to correct previous ver (#25652)
This commit is contained in:
Aimee Ukasick
@@ -12,7 +12,7 @@ We are pleased to announce the following Nomad updates.
|
||||
## Release highlights
|
||||
|
||||
- **Long Term Support Release (Enterprise):** Nomad 1.8 introduces a [long term
|
||||
support release](/nomad/docs/enterprise#long-term-support-lts-releases) which
|
||||
support release](/nomad/docs/v1.8.x/enterprise#long-term-support-lts-releases) which
|
||||
provides extended maintenance (two years of critical fixes provided through
|
||||
minor releases and efficient upgrades (support for direct upgrades from one
|
||||
LTS release to the next).
|
||||
@@ -25,7 +25,7 @@ We are pleased to announce the following Nomad updates.
|
||||
utility. Due these enhancements, tasks no longer require leveraging
|
||||
filesystem isolation based on chroot, which provide an enhanced security
|
||||
profile and improved performance for the Nomad operator. Refer to [Exec2 Task
|
||||
Driver](/nomad/plugins/v1.8.x/drivers/exec2) for more details.
|
||||
Driver](/nomad/plugins/drivers/exec2) for more details.
|
||||
|
||||
- **Transparent proxy support for Consul service mesh:** Transparent Proxy
|
||||
introduces a more seamless way of dialing upstream services when Consul service
|
||||
@@ -65,10 +65,10 @@ We are pleased to announce the following Nomad updates.
|
||||
on-page will be reflected in the status of that job in real-time.
|
||||
|
||||
- **Time based task execution (Enterprise) :** Using a CRON-like syntax, operators can now
|
||||
[schedule](/nomad/docs/job-specification/schedule) when tasks should execute
|
||||
[schedule](/nomad/docs/v1.8.x/job-specification/schedule) when tasks should execute
|
||||
and when they should stop. This provides governance for tasks executed from
|
||||
jobs, and allows operators to easily opt-in or opt-out of a schedule that
|
||||
governs when the task can run through the web based UI or through the [CLI](/nomad/docs/commands/alloc/pause).
|
||||
governs when the task can run through the web based UI or through the [CLI](/nomad/docs/v1.8.x/commands/alloc/pause).
|
||||
|
||||
- **Sentinel policy management in the Web UI (Enterprise):** Enterprise users can manage
|
||||
Sentinel policies directly within the Nomad UI. Users can create a Sentinel
|
||||
@@ -92,17 +92,17 @@ We are pleased to announce the following Nomad updates.
|
||||
Driver](/nomad/plugins/drivers/community/lxc) is now deprecated. Official
|
||||
support will be removed and the repo will be archived when Nomad 1.9 is
|
||||
released. Users are encouraged to migrate their workloads to another task
|
||||
driver such as the built-in Docker task [driver](/nomad/docs/drivers/docker).
|
||||
driver such as the built-in Docker task [driver](/nomad/docs/v1.8.x/drivers/docker).
|
||||
|
||||
- **ECS Task driver:** The remote [ECS Task
|
||||
Driver](https://developer.hashicorp.com/nomad/plugins/drivers/remote/ecs) is
|
||||
Driver](/nomad/plugins/drivers/remote/ecs) is
|
||||
now deprecated. Official support will be removed and the repo will be
|
||||
archived when Nomad 1.9 is released. Users are encouraged to migrate their
|
||||
workloads to Amazon ECS or to another Nomad task driver.
|
||||
|
||||
- **`stop_after_client_disconnect`, `max_client_disconnect`,
|
||||
`prevent_reschedule_on_lost`:** Nomad 1.8.0 introduces a
|
||||
[disconnect](/nomad/docs/job-specification/disconnect) block meant to group
|
||||
[disconnect](/nomad/docs/v1.8.x/job-specification/disconnect) block meant to group
|
||||
all the configuration options related to disconnected client's and server's
|
||||
behavior, causing the deprecation of the fields stop_after_client_disconnect,
|
||||
max_client_disconnect and prevent_reschedule_on_lost. This block also
|
||||
@@ -123,7 +123,7 @@ We are pleased to announce the following Nomad updates.
|
||||
## Upgrading
|
||||
|
||||
For more detailed information, please refer to the [upgrade details
|
||||
page](/nomad/docs/upgrade/upgrade-specific#nomad-1-8-0) and the changelogs.
|
||||
page](/nomad/docs/v1.8.x/upgrade/upgrade-specific#nomad-1-8-0) and the changelogs.
|
||||
|
||||
## Known issues
|
||||
|
||||
|
||||
@@ -18,24 +18,24 @@ MIGs. Refer to the [NVIDIA driver docs](/nomad/plugins/devices/nvidia) for
|
||||
details.
|
||||
|
||||
- **Quotas for device resources (Enterprise)**: This release extends quotas to
|
||||
allow limiting [device resources](/nomad/docs/job-specification/device). Refer
|
||||
to [Resource quotas](/nomad/docs/other-specifications/quota) for configuration details.
|
||||
allow limiting [device resources](/nomad/docs/v1.9.x/job-specification/device). Refer
|
||||
to [Resource quotas](/nomad/docs/v1.9.x/other-specifications/quota) for configuration details.
|
||||
|
||||
- **NUMA awareness for device resources (Enterprise)**: Nomad is able to
|
||||
correlate CPU cores with memory nodes and assign tasks to run on specific CPU
|
||||
cores so as to minimize any cross-memory node access patterns. With Nomad 1.9,
|
||||
we are expanding this functionality to also correlate
|
||||
[devices](/nomad/docs/concepts/plugins/devices) to memory nodes and enable
|
||||
[devices](/nomad/docs/v1.9.x/concepts/plugins/devices) to memory nodes and enable
|
||||
NUMA-aware scheduling to take device associativity into account when making
|
||||
scheduling decisions. Refer to [numa
|
||||
Block](/nomad/docs/job-specification/numa) for configuration details.
|
||||
Block](/nomad/docs/v1.9.x/job-specification/numa) for configuration details.
|
||||
|
||||
- **Golden job versions**: This feature introduces a way to preserve and compare
|
||||
historical versions of a job. Prior to this, any change to a job would push
|
||||
older versions into garbage collection. Now, you can tag a version to save it
|
||||
from garbage collection. Additionally, you can compare job versions by tag
|
||||
name and revert by tag name. Refer to [Job
|
||||
versions](/nomad/docs/concepts/job.mdx#job-versions) for details and links to
|
||||
versions](/nomad/docs/v1.9.x/concepts/job.mdx#job-versions) for details and links to
|
||||
how to use job version tagging.
|
||||
|
||||
- **Virt task driver (beta)**: The new Virt task driver uses
|
||||
@@ -99,7 +99,7 @@ The following are deprecated and will be removed in 1.10.
|
||||
|
||||
- Support for HCLv1 job specifications and the `-hcl1` flag on `nomad job run` and other commands. Refer to [GH-20195](https://github.com/hashicorp/nomad/issues/20195) for more details.
|
||||
|
||||
- Support for Nomad client agents older than v1.6.0. Older nodes will fail heartbeats. Nomad servers will mark the workloads on Nomad client agents older than 1.6.0 as lost and reschedule them normally according to the job's [reschedule](/nomad/docs/job-specification/reschedule) block.
|
||||
- Support for Nomad client agents older than v1.6.0. Older nodes will fail heartbeats. Nomad servers will mark the workloads on Nomad client agents older than 1.6.0 as lost and reschedule them normally according to the job's [reschedule](/nomad/docs/v1.9.x/job-specification/reschedule) block.
|
||||
|
||||
- The [LXC task driver](https://github.com/hashicorp/nomad-driver-lxc) and [ECS
|
||||
task driver](https://github.com/hashicorp/nomad-driver-ecs) projects have been
|
||||
@@ -107,13 +107,13 @@ The following are deprecated and will be removed in 1.10.
|
||||
plug-ins are maintained separately from the Nomad core project and are not
|
||||
subject to the LTS program.
|
||||
|
||||
- Nomad has removed the `tls_prefer_server_cipher_suites` agent configuration from the [`tls` block](/nomad/docs/configuration/tls).
|
||||
- Nomad has removed the `tls_prefer_server_cipher_suites` agent configuration from the [`tls` block](/nomad/docs/v1.9.x/configuration/tls).
|
||||
|
||||
|
||||
## Upgrading
|
||||
|
||||
For more detailed information, please refer to the [upgrade details
|
||||
page](/nomad/docs/upgrade/upgrade-specific#nomad-1-9-0) and the changelogs.
|
||||
page](/nomad/docs/v1.9.x/upgrade/upgrade-specific#nomad-1-9-0) and the changelogs.
|
||||
|
||||
## Known issues
|
||||
|
||||
@@ -129,8 +129,8 @@ listed below.
|
||||
- [1.9.0](https://github.com/hashicorp/nomad/releases/tag/v1.9.0)
|
||||
|
||||
|
||||
[consul-integration]: /nomad/docs/integrations/consul/acl
|
||||
[vault-integration]: /nomad/docs/integrations/vault/acl
|
||||
[consul-integration]: /nomad/docs/v1.9.x/integrations/consul/acl
|
||||
[vault-integration]: /nomad/docs/v1.9.x/integrations/vault/acl
|
||||
[GH-18529]: https://github.com/hashicorp/nomad/issues/18529
|
||||
[`disconnect`]: /nomad/docs/job-specification/disconnect
|
||||
[Resource Quotas]: /nomad/docs/other-specifications/quota
|
||||
[`disconnect`]: /nomad/docs/v1.9.x/job-specification/disconnect
|
||||
[Resource Quotas]: /nomad/docs/v1.9.x/other-specifications/quota
|
||||
|
||||
@@ -60,10 +60,10 @@ Linux distribution's package manager.
|
||||
In Nomad 1.9.4, the default `function_denylist` includes `executeTemplate`, as
|
||||
a measure to prevent accidental or malicious infinitely recursive execution.
|
||||
Users that require `executeTemplate` should update their
|
||||
[configuration](/nomad/docs/job-specification/template#function_denylist).
|
||||
[configuration](/nomad/docs/v1.9.x/job-specification/template#function_denylist).
|
||||
|
||||
Additionally, the [default client env deny
|
||||
list](/nomad/docs/configuration/client#env-denylist) includes more environment
|
||||
list](/nomad/docs/v1.9.x/configuration/client#env-denylist) includes more environment
|
||||
variables. Users who need some of these secure environment variables passed to
|
||||
their tasks should consult the list and overwrite it in the configuration.
|
||||
|
||||
@@ -92,13 +92,13 @@ block.
|
||||
Nomad 1.9.0 stores keys used for signing Workload Identity and encrypting
|
||||
Variables in Raft, instead of storing key material in the external
|
||||
keystore. When using external KMS or Vault transit encryption for the
|
||||
[`keyring`](/nomad/docs/configuration/keyring) provider, the key encryption key
|
||||
[`keyring`](/nomad/docs/v1.9.x/configuration/keyring) provider, the key encryption key
|
||||
(KEK) is stored outside of Nomad and no cleartext key material exists on disk.
|
||||
When using the default AEAD provider, the key encryption key (KEK) is stored in
|
||||
Raft alongside the encrypted data encryption keys (DEK).
|
||||
|
||||
Nomad automatically migrates the key storage for all key material on the
|
||||
first [`root_key_gc_interval`](/nomad/docs/configuration/server#root_key_gc_interval) after all servers are upgraded to 1.9.0. The
|
||||
first [`root_key_gc_interval`](/nomad/docs/v1.9.x/configuration/server#root_key_gc_interval) after all servers are upgraded to 1.9.0. The
|
||||
existing on-disk keystore is required to restore servers from older snapshots,
|
||||
so you should continue to back up the on-disk keystore until you no longer need
|
||||
those older snapshots.
|
||||
@@ -110,7 +110,7 @@ the `-hcl1` option for the `job run`, `job plan`, and `job validate` commands
|
||||
will no longer work.
|
||||
|
||||
One common use of `-hcl1` was when specifying [Docker
|
||||
labels](/nomad/docs/drivers/docker#labels) with dots in their keys such as for
|
||||
labels](/nomad/docs/v1.9.x/drivers/docker#labels) with dots in their keys such as for
|
||||
DataDog autodiscovery:
|
||||
|
||||
```hcl
|
||||
|
||||
@@ -9,10 +9,10 @@ This table lists removed Vault fields and the new workflow.
|
||||
|
||||
| Field | Configuration | New Workflow |
|
||||
| ------ | ------------ | ------------ |
|
||||
| [`vault.allow_unauthenticated`](/nomad/docs/v1.8.x/configuration/vault#allow_unauthenticated) | Agent | Tasks should use a workload identity. Do not use a Vault token. |
|
||||
| [`vault.task_token_ttl`]( /nomad/docs/v1.8.x/configuration/vault#task_token_ttl) | Agent | With workload identity, tasks receive their TTL configuration from the Vault role. |
|
||||
| [`vault.token`](/nomad/docs/v1.8.x/configuration/vault#token) | Agent | Nomad agents use the workload identity when making requests to authenticated endpoints. |
|
||||
| [`vault.policies`](/nomad/docs/v1.8.x/job-specification/vault#policies) | Job specification | Configure and use a Vault role. |
|
||||
| [`vault.allow_unauthenticated`](/nomad/docs/v1.9.x/configuration/vault#allow_unauthenticated) | Agent | Tasks should use a workload identity. Do not use a Vault token. |
|
||||
| [`vault.task_token_ttl`]( /nomad/docs/v1.9.x/configuration/vault#task_token_ttl) | Agent | With workload identity, tasks receive their TTL configuration from the Vault role. |
|
||||
| [`vault.token`](/nomad/docs/v1.9.x/configuration/vault#token) | Agent | Nomad agents use the workload identity when making requests to authenticated endpoints. |
|
||||
| [`vault.policies`](/nomad/docs/v1.9.x/job-specification/vault#policies) | Job specification | Configure and use a Vault role. |
|
||||
|
||||
Before upgrading to Nomad 1.10, perform the following tasks:
|
||||
|
||||
@@ -21,5 +21,5 @@ Before upgrading to Nomad 1.10, perform the following tasks:
|
||||
|
||||
Refer to the following guides for more information:
|
||||
|
||||
- [Migrating to using workload identity with Vault](/nomad/docs/v1.8.x/integrations/vault/acl#migrating-to-using-workload-identity-with-vault)
|
||||
- [Migrating to using workload identity with Consul](/nomad/docs/v1.8.x/integrations/consul/acl#migrating-to-using-workload-identity-with-consul)
|
||||
- [Migrating to using workload identity with Vault](/nomad/docs/v1.9.x/integrations/vault/acl#migrating-to-using-workload-identity-with-vault)
|
||||
- [Migrating to using workload identity with Consul](/nomad/docs/v1.9.x/integrations/consul/acl#migrating-to-using-workload-identity-with-consul)
|
||||
|
||||
Reference in New Issue
Block a user