From 530a35802a8fa37933526fd4a9b331e17127d1ad Mon Sep 17 00:00:00 2001 From: Derek Nola Date: Mon, 3 Jan 2022 14:58:16 -0800 Subject: [PATCH 1/2] Duplicate note warning HA K3s about not enabling secrets later Signed-off-by: Derek Nola --- content/k3s/latest/en/security/secrets_encryption/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/k3s/latest/en/security/secrets_encryption/_index.md b/content/k3s/latest/en/security/secrets_encryption/_index.md index b91bc4d081a..c7a23d4f90c 100644 --- a/content/k3s/latest/en/security/secrets_encryption/_index.md +++ b/content/k3s/latest/en/security/secrets_encryption/_index.md @@ -87,6 +87,8 @@ The steps are the same for both embedded DB and external DB clusters. To rotate secrets encryption keys on HA setups: +>**Note:** Starting K3s without encryption and enabling it at a later time is currently *not* supported. + >**Note:** While not required, it is recommended that you pick one server node from which to run the `secrets-encrypt` commands. - Start up all three K3s servers with the `--secrets-encryption` flag. For brevity, the servers will be referred to as S1, S2, S3. From f4bc78ee0c174e39598c006a8f7cd0ad37255260 Mon Sep 17 00:00:00 2001 From: Jennifer Travinski Date: Tue, 4 Jan 2022 10:59:41 -0500 Subject: [PATCH 2/2] Grouped notes together as bullet points --- .../k3s/latest/en/security/secrets_encryption/_index.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/content/k3s/latest/en/security/secrets_encryption/_index.md b/content/k3s/latest/en/security/secrets_encryption/_index.md index c7a23d4f90c..a7491e2fb63 100644 --- a/content/k3s/latest/en/security/secrets_encryption/_index.md +++ b/content/k3s/latest/en/security/secrets_encryption/_index.md @@ -87,9 +87,11 @@ The steps are the same for both embedded DB and external DB clusters. To rotate secrets encryption keys on HA setups: ->**Note:** Starting K3s without encryption and enabling it at a later time is currently *not* supported. - ->**Note:** While not required, it is recommended that you pick one server node from which to run the `secrets-encrypt` commands. +>**Notes:** +> +> - Starting K3s without encryption and enabling it at a later time is currently *not* supported. +> +> - While not required, it is recommended that you pick one server node from which to run the `secrets-encrypt` commands. - Start up all three K3s servers with the `--secrets-encryption` flag. For brevity, the servers will be referred to as S1, S2, S3.