feat: prepare mi mock information for backend but do not set it in the deployment yet - #4243
Merged
openshift-merge-bot[bot] merged 1 commit intoMar 6, 2026
Conversation
…e deployment yet We prepare the backend component to be able to reference the MI mock information. It also includes the conditional configuration of the MI mock identity certificate bundle in backend's ServiceProviderClass. Also introduces a new config.yaml attribute miMockTenantId. Although the configuration is introduced and prepared the backend deployment does not leverage it yet.
openshift-ci
Bot
requested review from
Gerd Oberlechner (geoberle) and
Jan-Hendrik Boll (janboll)
February 27, 2026 11:30
Collaborator
Author
|
/hold |
Collaborator
Author
|
Once this is merged we will need to update the config.yaml of the ARO-HCP integration environment to configure the |
Collaborator
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: geoberle, miguelsorianod The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Collaborator
Author
|
/hold cancel |
Collaborator
|
/retest |
Collaborator
|
/test e2e-parallel |
Collaborator
|
/retest |
6 similar comments
Collaborator
Author
|
/retest |
Collaborator
Author
|
/retest |
Collaborator
Author
|
/retest |
Collaborator
Author
|
/retest |
Collaborator
Author
|
/retest |
Collaborator
Author
|
/retest |
openshift-merge-bot
Bot
deleted the
msoriano-prepare-mimock-deploy-backendcfg
branch
March 6, 2026 15:23
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
In #3820 we are going to introduce a validation that interacts with Microsoft's Managed Identities Data Plane service in the ARO-HCP environments where it is available. In the environments where it is not available it is not possible to retrieve credentials associated to Managed Identities. In those environments we instead have a fake implementation of the Managed Identities Data Plane client that always returns the credentials associated to common Azure Service Principal identity that we commonly refer to as the MI mock identity (or MSI Mock identity).
A prerequisite to be able to introduce #3820 is to first rollout the configuration at the deployment level of the MSI Mock identity which changes per ARO-HCP environment. This MR introduces it.
We prepare the backend component to be able to reference the MI mock information.
It also includes the conditional configuration of the MI mock identity certificate bundle in backend's ServiceProviderClass.
Also introduces a new config.yaml attribute miMockTenantId.
Although the configuration is introduced and prepared the backend deployment does not leverage it yet.