Skip to content

Conversation

@BobbyRadford
Copy link
Contributor

@BobbyRadford BobbyRadford commented May 20, 2021

Support the IBMCloud platform in Passthrough mode for IPI/UPI.

Related to: openshift/enhancements#773

Support the IBMCloud platform in Passthrough mode for IPI/UPI.
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 20, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 20, 2021

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BobbyRadford
To complete the pull request process, please assign csrwng after the PR has been reviewed.
You can assign the PR to them by writing /assign @csrwng in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot requested review from dgoodwin and twiest May 20, 2021 15:37
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 20, 2021

Hi @BobbyRadford. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci openshift-ci bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 20, 2021
@BobbyRadford BobbyRadford marked this pull request as ready for review May 20, 2021 19:00
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 20, 2021
@gregsheremeta
Copy link
Contributor

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 20, 2021
@BobbyRadford
Copy link
Contributor Author

/test all

@joelddiaz
Copy link
Contributor

@dgoodwin are we still accepting new platform enablement of this style (where CCO is doing in-cluster processing of CredentialsRequests)?

@dgoodwin
Copy link
Contributor

@BobbyRadford per Joel's comment above, we are wondering if you would be willing to be an early adopter of our new approach to new platforms in CCO.

We have some docs on how we want this to work going forward that will merge once the window opens for next release: #326

Essentially over the past few years of openshift 4 we have learned that customers prefer (a) fine grained least privileged for each component, and (b) the cluster not having admin level credentials. We're now moving away from mint and passthough mode (especially for new platforms) instead opting for manual mode, with ccoctl utility for admins to manually mint their credentials.

For this PR we'd love to have IBM cloud be a fully supported best practice implementation within CCO which would mean:

  • Add support for specifying precise permissions each OpenShift component needs in IBM Cloud.
  • Drop passthrough support and instead just support manual.
  • Implement IBM Cloud minting in the ccoctl tool discussed in the above doc PR.

Lets us know what you think here, or find Joel or I on slack.

@jeffnowicki
Copy link

@dgoodwin - thank you for the feedback and nudge to look at the new CCO approach. We are in 100% agreement on the preference for fine-grain component-level privilege control and removal of admin level credentials from the cluster. OCP 4.9 will be the first release for IBM Cloud platform support. The timeline we have is extremely tight and we have significant amount of work to complete. Decisions have been made that would keep us on this timeline. One of those decisions (discussed with Katherine Dube and RH team) was to support “passthrough” only in our genesis effort. We would be in a better position to look at this support as an update on a 4.10 timeline.

@joelddiaz
Copy link
Contributor

FWIW, using the Manual mode approach doesn't mean you must use fine-grained permissions. Manual mode just means that there is no in-cluster handling of cloud credentials data.

It is entirely possible to just put the same credentials secret data into each generated Secret manifests when using Manual mode (which is precisely how things work when doing an install on AWS in an environment where the IAM API endpoints are not available, and the cloud-cred-operator cannot do it's normal mode of operation). But extending ccoctl for this kind of copy-the-same-secret-data-over-and-over-again operation does seem a bit pointless.

@BobbyRadford
Copy link
Contributor Author

Closing this in light of the new PR for Manual mode: #356

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants