Set cluster source during binding

[dcberg]

In IBM Cloud when you create a service binding within Cloud Foundry you will see the Cloud Foundry app in the Connections list of the service. When you use the Cloud Operator to create a binding there is no connection listing back to the cluster with the operator. Instead you will see an entry under the Service Credentials section with an auto generated key (not all that useful).

The binding API does allow for a source CRN to be passed. The source CRN can be obtained from the cluster-info ConfigMap within the cluster. This CRN should be passed when creating the binding. The service connections support may need to be modified slightly to not assume Cloud Foundry as the source but this should be fairly simple to do.

[vazirim]

• Is this for credentials of CF services only, or CF and non-CF?

• If this needs to work for bindings of CF services, could you give me an example of a CF service? (there are very few CF services out there now)

• For non-CF, we are passing the service crn as the SourceCRN currently. But this doesn't manifest anywhere in the console UI for credentials. What is the behavior that is expected here?

[dcberg]

This needs to work for non CF connections. In this case the source of the connection is a cluster managed in IBM Cloud.

If you are already passing the crn of the cluster then there may be nothing to do on the operator side and it requires a fix on the service side....crossing fingers. :)

[vazirim]

We are passing the crn of the service to which the credentials belong. So I will change that to be the cluster CRN.

[vazirim]

@dcberg When I pass the cluster CRN at credential creation, I get this error: {"message":"Failed to get the instance information for the given source_crn","status_code":400,"transaction_id":"bss-a746e0736830995e"}

It seems that a cluster is a different kind of service. Are you sure that the credential creation API can handle that? The cluster CRN doesn't have a ScopeType, Resource, and ResourceType.