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

Provide component binding/linking

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • OpenShift 4.3
    • None
    • Service Binding
    • None
    • Component binding
    • To Do
    • QE Needed, Docs Needed, TE Needed, Customer Facing
    • 0% To Do, 0% In Progress, 100% Done

      Problem

      As a Developer, I don't want to know details about how to connect two application components together (secrets, configmaps, env var injection into deployments, ....), I want to just declare my intent and the linking is handled.

      Acceptance Criteria

      1. Verify that AppBinding (or whatever it is called) CRD/operator is installed
      2. Verify that non-cluster-admins can create AppBinding CRs with the default permissions they get with a project
      3. Verify that when AppBinding POST/creation request is successfully sent, that the source component is injected with the target component/service configuration and source pods are appropriately restarted to pick up the configuration changes

      References

      • OLM Epic PROD-1067
      • AppBinding proposal
      • K8S Service Catalog / Broker & OpenServiceBrokerAPI, namely Service Binding

      Epic Brief

              shbose Shoubhik Bose
              sspeiche@redhat.com Steve Speicher (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: