[Release-1.22] Create encryption hash file if it doesn't exist #5169
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
brandond
approved these changes
Feb 25, 2022
Signed-off-by: Derek Nola <derek.nola@suse.com>
dereknola
force-pushed
the
se_upgrade_hash_122
branch
from
8dd5796
to
ff822cc
Compare
This was referenced Mar 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Backport of #5140
Signed-off-by: Derek Nola derek.nola@suse.com
Proposed Changes
Check and make sure the
encryption-hash.jsonfile exists when generating secrets-encryption files.This was breaking upgrades because previously we only had one relevant encryption-config.json file.
Types of Changes
Bugfix
Verification
k3s server --secrets-encryptionk3s server --secrets-encryptionk3s secrets-encrypt statusand note that it does not fail with 500 Internal Server ErrorLinked Issues
#5166
User-Facing Change
Further Comments