Skip to content

Support version 1.0.0-rc2 of Service Binding Spec and Custom Projection Extension  #154

Open

Description

@ron1

Feature Request

Support version 1.0.0-rc2 of Service Binding Spec and Custom Projection Extension. Validate this functionality by testing against the latest version of VMWare Labs Service Bindings.

Is your feature request related to a problem?

The service bindings functionality offered by the latest versions of the IBM Runtime Component Operator and the Red Hat Service Binding Operator is quite limited when compared to version 1.0.0-rc2 of the Service Binding spec. Several issues prevent me from using the existing RCO/SBO capabilty not the least of which is SBO issue redhat-developer/service-binding-operator#389 which prevents the use of Secrets as direct binding resources.

Describe the solution you'd like

The VMWare Labs Service Bindings implementation appears to be compliant with the 1.0.0-rc2 version of the Service Bindings Spec including the Custom Projection Extension and appears to be maturing quickly. This feature will allow me to E2E test my RCO-enabled application with bindings to multiple backing services exposed via a Service Binding Spec implementation.

Activity

  1. navidsh commented on Aug 5, 2020

    @navidsh
    Member

    Thanks @ron1 for opening this issue.
    Complying to the service binding spec is in our near future plan. There are already some issues on the SBO side to address this.

  2. ron1 commented on Aug 17, 2020

    @ron1
    Author

    @navidsh I suspect it may take a while for the SBO to support version 1.0.0-rc2+ of the Service Binding Spec given their other priorities as well as their backwards compatibility burdens. Does the RCO team plan to wait for a Spec-compliant version of the SBO before it delivers a Spec-compliant version of RCO?

  3. arthurdm commented on Aug 17, 2020

    @arthurdm
    Member

    @ron1 - I agree with your assessment of SBO. We're still trying to pursue that as the main option, but we have may have to look at options inside RCO indeed. It all depends on the conversations we're having at the spec level about having a reference implementation of a controller we could all rally behind.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions