[kots] ensure secret creation for inCluster registry backend #10256
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
roboquat
added
do-not-merge/release-note-label-needed
size/XS
release-note-none
and removed
do-not-merge/release-note-label-needed
labels
github-actions
bot
added
do-not-merge/release-note-label-needed
team: delivery
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.
Description
This fixes the currently existing bug, which prevents creation of secret for
s3when once choosess3forinClusterregistry storage backend.Related Issue(s)
Fixes #
How to test
Currently if you try to use
s3as the storage backend forinClusterregistry, you will get an error when creating workspace.Release Notes
Documentation