Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix MIWI Cluster update flow to add new openshift operator identity #4037

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

rajdeepc2792
Copy link
Collaborator

@rajdeepc2792 rajdeepc2792 commented Jan 3, 2025

Which issue this PR addresses:

Fixes https://issues.redhat.com/browse/ARO-13916
https://issues.redhat.com/browse/ARO-13924

What this PR does / why we need it:

When adding a new OpenShift Identity to an existing cluster, the federated identity and secret in the cluster must be created.
During testing 2 issues were found, this PR fixes them:

  1. ObjectID and ClientID are not populated during update for the new operator identity
  2. For secret creation, the namespace must exist, so create the namespaces before secret creation.

Test plan for issue:

[x] Unit Tests
[x] Test the cluster update in local

Is there any documentation that needs to be updated for this PR?

No

How do you know this will function as expected in production?

Feature not available in production.

Copy link
Collaborator

@cadenmarchese cadenmarchese left a comment

Choose a reason for hiding this comment

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

thanks for the fix!

)
}

s = append(s, steps.AuthorizationRetryingAction(m.fpAuthorizer, m.validateResources))
Copy link
Contributor

Choose a reason for hiding this comment

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

Why does this need to be moved down here? I'm thinking that now we could end up with situations where a cx passes a valid MI resource ID, and we either persist its object/client IDs to the cluster doc (or error out with lack of permission trying to do so) before we make it to dynamic validation, which would give the cx a more helpful error message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working chainsaw Pull requests or issues owned by Team Chainsaw ready-for-review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants