OADP-602 Create keyfile for each secret name for GCS Registry Driver #163
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
openshift-ci
bot
added
the
do-not-merge/work-in-progress
kaovilai
force-pushed
the
gcs-credentials
branch
from
11284a7
to
23db272
Compare
kaovilai
changed the title
…a path to registry GCS driver
kaovilai
force-pushed
the
gcs-credentials
branch
from
23db272
to
b9ba226
Compare
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
sseago
approved these changes
Aug 10, 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.
Fixes registry failures on imagestream backups when velero deployment created does not have GCS secret mounted ie. no VSL specified.
This PR create a keyfile for each secret name used in GCP BSL so we can give a path to registry GCS driver
OADP-602