-
Epic
-
Resolution: Done
-
Major
-
None
-
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
- Verify that AppBinding (or whatever it is called) CRD/operator is installed
- Verify that non-cluster-admins can create AppBinding CRs with the default permissions they get with a project
- 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
- is cloned by
-
APPSVC-151 R&D E2E app dev scenario
- Closed