Skip to content

Update migration steps for secrets encryption provider #550

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
manuelbuil merged 1 commit into from
May 22, 2026
Merged

Update migration steps for secrets encryption provider #550

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/security/secrets_encryption.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,12 @@ RKE2 supports the following [encryption providers](https://kubernetes.io/docs/ta
#### Migrating Providers
You can migrate from the `aescbc` provider to the `secretbox` provider by following these steps:
1. Ensure that the `secretbox` provider is supported by your RKE2 version.
2. Update/Add the `secrets-encryption-provider` flag in your RKE2 configuration file to `secretbox`.
3. Rotate the encryption keys, following the [Encryption Key Rotation](#encryption-key-rotation) section below.
2. Update/Add the `secrets-encryption-provider` flag in the RKE2 configuration file on your server nodes to `secretbox`.
3. Sequentially restart RKE2 on the server nodes, to load the new configuration:
```
systemctl restart rke2-server.service
```
4. Rotate the encryption keys, following the [Encryption Key Rotation](#encryption-key-rotation) section below.

### Generated encryption config file

Expand Down
Loading