Skip to content

Conversation

@mrWinston
Copy link
Collaborator

Which issue this PR addresses:

Fixes ARO-22664

What this PR does / why we need it:

This PR modifies the cluster Keyvault and Certificate clients to use the RPs Managed identity instead of the first party credentials. This is needed as part of the epic to bring our INT environment back.
The INT RP needs to use "fake" FP credentials, meaning we'll create an azure application to fill the same role. Due to security restrictions however, those "fake" credentials can't be used across multiple subscriptions. And because the new int setup will have the RP live in a different subscription than the clusters it creates, we can't use the same "fake" FP credential in both the cluster subscription and the RP subscription.

But we don't need to anyway, as we can just remove any usage of the FP credential in the RP subscription and use the RPs managed identity for that.

There's an accompanying RP in sdp-pipelines to give RP MSI the missing permissions: https://msazure.visualstudio.com/AzureRedHatOpenShift/_git/sdp-pipelines/pullrequest/14222081

Test plan for issue:

  • Will need to be tested together with the sdp pipelines PR in Canary before merging

- and rename m.ch to a more descriptive name
@mrWinston mrWinston force-pushed the ARO-22664-use-managed-identity-for-cert-creation branch from b9873b9 to 9772634 Compare December 11, 2025 08:36
Copy link
Contributor

@mociarain mociarain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Added DNM until the testing is complete

@mociarain mociarain changed the title [ARO-22664] use RP managed identity instead of local fp service principal for az clients in cluster creation [DNM] [ARO-22664] use RP managed identity instead of local fp service principal for az clients in cluster creation Jan 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants