Mirror/k3s
1
0
Fork 0
mirror of https://github.com/k3s-io/k3s.git synced 2024-06-07 19:41:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

Typo fix

Browse Source 
Signed-off-by: Derek Nola <derek.nola@suse.com>
This commit is contained in:
Derek Nola 2023-09-14 09:28:44 -07:00
parent 5c5d957e73
commit bd9dad87d5
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/adrs/server-token-rotation.md
View File

@ -53,7 +53,7 @@ Admins can then use the new token value to rejoin existing server nodes or join
Similar to the `k3s certificate rotate` and the `k3s secret-encrypt rotate-keys` subcommands, Similar to the `k3s certificate rotate` and the `k3s secret-encrypt rotate-keys` subcommands,
the `k3s token rotate` subcommand will be wrapper for an API request to the server to perform the decryption the `k3s token rotate` subcommand will be wrapper for an API request to the server to perform the decryption
with the old token, and then reencryption of the bootstrap data with the new token. After reenecryption, the with the old token, and then reencryption of the bootstrap data with the new token. After reenecryption, the
bootstrap data will be updated with the modified token and passwrd files, allowing propgation of the files to bootstrap data will be updated with the modified token and password files, allowing propagation of the files to
existing servers upon restart. existing servers upon restart.
### Token Rotation Workflow ### Token Rotation Workflow
@ -87,8 +87,8 @@ systemctl start k3s
## Decision ## Decision
We will procced forward with the above implementation. We will proceed forward with the above implementation.
## Consequences ## Consequences
Documentation the is explicit around the cluster token is compromised. Tt's strongly recommend to do a clean cluster reinstall, since this is the only way to be sure of the cluster's security state - eliminating the possibility that backdoors could have been planted by a malicious user". Documentation is explicit around what to do if the cluster token is compromised. It's strongly recommend to do a clean cluster reinstall, since this is the only way to be sure of the cluster's security state - eliminating the possibility that backdoors could have been planted by a malicious user.