Enable secret encryption on existing clusters #13370
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Types of Changes
k3s secrets-encrypt enableon clusters that do no have--secrets-encryption. Places an encryption config with the identity provider. Users can then enable actual encryption by rotating the keys viak3s secrets-encrypt rotate-keysVerification
k3s secrets-encrypt status, should be disabledk3s secrets-encrypt enableon a single server--secrets-encryptionk3s secrets-encrypt status, still disabled, but with thestage: startk3s secrets-encrypt rotate-keyson a single serverk3s secrets-encrypt status, should be enabled with aescbcTesting
Covered
Linked Issues
#7195
User-Facing Change
Further Comments
Need to expand docs with a guide on how to do this.