Goals

A public specification for Service Binding have been authored by multiple actors from the community:

https://github.com/k8s-service-bindings/spec

We have been taking part of the specification effort, but there are some subtilities and API details that our current implementation is not aligned with.

The specification is going to be GA at the end of March. As such, there will be some traction and engagement that is going to be started, by backing services provider. 

We want to reconcile with the specification.

Compliance: Support the specification at API level

• Specification is going to be GA end of March
• Drive community awareness of Service Binding
• Bring more values for partners to support the spec, and support other K8s distribution
• Can collaborate with other vendors to get more interested partners - we can’t do that alone

Rationalization: Leverage the opportunity to hardened our implementation.

• Security constraints 
• Performance issues
• Use cases that are not getting used at this moment

Evolve: Contribute to the spec to extend capabilities. Evolve along with the spec

Study work document:

https://docs.google.com/document/d/1GcwmdfqW30TDmH1Nx_chu4XBecF284FGVfRingmtGEE/edit#heading=h.jogq9nylsy8p