MIWI - Provide boundServiceAccountSigningKey secret to Hive Install #3877
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
1 task
tsatam
requested review from
jewzaam,
bennerv,
hawkowl,
rogbas,
petrkotas,
jharrington22,
cblecker,
cadenmarchese,
UlrichSchlueter,
SudoBrendan,
yjst2012,
jaitaiwan,
anshulvermapatel,
hlipsig,
tiguelu,
SrinivasAtmakuri,
mociarain,
kimorris27,
bitoku and
fahlmant
as code owners
|
/azp run ci,e2e |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run e2e |
|
Azure Pipelines successfully started running 1 pipeline(s). |
bennerv
approved these changes
Oct 4, 2024
bennerv
deleted the
tsatam/ARO-4374-provide-boundsasigningkey-secret-to-hive-install
branch
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.
Which issue this PR addresses:
Fixes ARO-4374
What this PR does / why we need it:
bound-service-account-signing-keysecret to the Hive cluster installation. This secret will be picked up by a companion PR (MIWI - Explicitly load the BoundSASigningKey asset and add it to the install graph openshift/installer-aro-wrapper#174) to the ARO Installer wrapper that emulates the behavior of the upstream OpenShift installer to provide this signing key as an installation asset (e.g. https://github.com/openshift/installer/blob/release-4.14/pkg/asset/tls/boundsasigningkey.go)Test plan for issue:
Is there any documentation that needs to be updated for this PR?
No
How do you know this will function as expected in production?