Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-414

Support binding to a backing service in a different namespace

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • OpenShift 4.4
    • None
    • Service Binding
    • None

      Copy from https://github.com/redhat-developer/service-binding-operator/issues/314:

      "We have the requirement to be able to connect a BackingService in one namespace and an Application in another.

      Is there a way to handle this already? If not, can we extend the spec to allow this? The binding secret would need to be created in the Application namespace, but I don't see a reason that wouldn't work."

      apiVersion: apps.openshift.io/v1alpha1
kind: ServiceBindingRequest
metadata:
  name: nodejs-rest-http-crud-dc-demo-database-postgresql-d
  namespace: sbose
spec:
  applicationSelector:
    group: apps.openshift.io
    resource: deploymentconfigs
    resourceRef: nodejs-rest-http-crud
    version: v1
  backingServiceSelector:
    group: postgresql.baiju.dev
    namespace: bar
    kind: Database
    resourceRef: demo-database
    version: v1alpha1
  backingServiceSelectors: null
  detectBindingResources: true

      Every backing service could have a `namespace` as well once https://github.com/redhat-developer/service-binding-operator/pull/322 is in.

              Unassigned Unassigned
              isuttonl Igor Sutton (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: