Story (Required)

As a Service vendor, I would like to understand what are the ways to make Service bindable, so that service binding operator can easily find relevant bindings and inject them into applications.

Background (Required)

We would like to spead the word about SBO and work on its adoption. Hence, we need to share with the vendors what are their options to get aligned to service binding approach.

Approach(Required)

Introduce story about binding secret, explain that operators can create those that can be consumed directly without modification, or SBO can create binding secret based on found bindings.

Document all possible options:

• Provisioned Service
• Direct Secret Reference
• Expose bindings in resources owned by the service
• Define binding data locations using annotations
• Define binding data locations using CSV descriptions

Also:

• Refer Service binding spec where appropriate
• Suggest best practices for new/existing operators
• State pros/cons of each approach if possible

Acceptance Criteria

The section should give guidance to service vendors how to adapt/write operators to be compliant with the service binding.

INVEST Checklist

Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated

Legend

Unknown
Verified
Unsatisfied