From 58cccb0c029ce39f666501ffa59fced70c6bc964 Mon Sep 17 00:00:00 2001 From: Tim Gross Date: Fri, 18 Feb 2022 10:50:40 -0500 Subject: [PATCH] docs: changelog and upgrade guide notes --- .changelog/12078.txt | 11 ++++++++ .../content/docs/upgrade/upgrade-specific.mdx | 25 +++++++++++++++++++ 2 files changed, 36 insertions(+) create mode 100644 .changelog/12078.txt diff --git a/.changelog/12078.txt b/.changelog/12078.txt new file mode 100644 index 000000000000..96e335d94c06 --- /dev/null +++ b/.changelog/12078.txt @@ -0,0 +1,11 @@ +```release-note:improvement +csi: Allow for concurrent plugin allocations +``` + +```release-note:breaking-change +client: The client state store will be automatically migrated to a new schema version when upgrading a client. Downgrading to a previous version of the client after upgrading it to Nomad 1.3 is not supported. To downgrade safely, users should erase the Nomad client's data directory. +``` + +```release-note:breaking-change +csi: The client filesystem layout for CSI plugins has been updated to correctly handle the lifecycle of multiple allocations serving the same plugin. Running plugin tasks will not be updated after upgrading the client, but it is recommended to redeploy CSI plugin jobs after upgrading the cluster. +``` diff --git a/website/content/docs/upgrade/upgrade-specific.mdx b/website/content/docs/upgrade/upgrade-specific.mdx index a29c28697988..b3750cc03374 100644 --- a/website/content/docs/upgrade/upgrade-specific.mdx +++ b/website/content/docs/upgrade/upgrade-specific.mdx @@ -25,6 +25,31 @@ In Nomad 1.3.0, the default raft protocol version has been updated to server will automatically upgrade that server's raft protocol. See the [Upgrading to Raft Protocol 3] guide. +#### Client State Store + +The client state store will be automatically migrated to a new schema +version when upgrading a client. Downgrading to a previous version of +the client after upgrading it to Nomad 1.3 is not supported. To +downgrade safely, users should erase the Nomad client's data +directory. + +#### CSI Plugins + +The client filesystem layout for CSI plugins has been updated to +correctly handle the lifecycle of multiple allocations serving the +same plugin. Running plugin tasks will not be updated after upgrading +the client, but it is recommended to redeploy CSI plugin jobs after +upgrading the cluster. + +The directory for plugin control sockets will be mounted from a new +per-allocation directory in the client data dir. This will still be +bind-mounted to `csi_plugin.mount_config` as in versions of Nomad +prior to 1.3.0. + +The volume staging directory for new CSI plugin tasks will now be +mounted to the task's `NOMAD_TASK_DIR` instead of the +`csi_plugin.mount_config`. + ## Nomad 1.2.6, 1.1.12, and 1.0.18 #### ACL requirement for the job parse endpoint