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

docs: upgrade docs should point at real version (#24438)

Browse Source 
Let users know what happened to 1.9.2 but label the gc change as the
first working release (1.9.3).
This commit is contained in:
Michael Schurter
2024-11-12 11:05:27 -08:00
committed by GitHub
parent b36c77781f
commit 8dd570d6ca
1 changed files with 9 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
website/content/docs/upgrade/upgrade-specific.mdx
View File

@@ -13,14 +13,17 @@ upgrade. However, specific versions of Nomad may have more details provided for
their upgrades as a result of new features or changed behavior. This page is
used to document those details separately from the standard upgrade flow.
## Nomad 1.9.2
## Nomad 1.9.3
In Nomad 1.9.2, the mechanism used for calculating when objects are eligible
In Nomad 1.9.3, the mechanism used for calculating when objects are eligible
for garbage collection changes to a clock-based one. This has two consequences.
First, it allows to set arbitrarily long GC intervals. Second, it requires that
Nomad servers are kept roughly in sync time-wise, because GC can originate in a
follower.
Nomad 1.9.2 contained a bug that could drop all cluster state on upgrade and
has been removed from downloads.
## Nomad 1.9.0
#### Dropped support for older clients
@@ -35,10 +38,10 @@ 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`][] 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).
[`keyring`](/nomad/docs/configuration/keyring) provider, the key encryption key
(KEK) is stored outside of Nomad and no cleartext key material exists on disk.
When using the default AEAD provider, the key encryption key (KEK) is stored in
Raft alongside the encrypted data encryption keys (DEK).
Nomad automatically migrates the key storage for all key material on the
first [`root_key_gc_interval`][] after all servers are upgraded to 1.9.0. The