Feature: Support Service Binding Specification for Kubernetes

[baijum]

Service Binding Specification for Kubernetes standardizes exposing backing service secrets to application workloads. A backing service is any process that the application consumes over the network as part of its regular operation. Examples include data stores (such as MySQL or MongoDB), caching servers (such as Memcached), and stream processing systems (such as Kafka).

The key benefit of supporting the spec for a backing service is that the Secret resource will be collected and exposed to application workloads consistently and predictably.

Few facts about the spec:

• The spec is a collective effort of a community working with Kubernetes.
• Contributions from many organizations including VMware, IBM, and Red Hat.
• The spec is matured and general availability release 1.0.0 came out in March 2022

The website has a good introduction to the expected behavior of Service providers.

Service providers expose bindings through a Secret resource with data required for connectivity. The specification’s Provisioned Service section describes this in detail.

I propose Azure Service Operator support the Provisioned Service API.

[theunrepentantgeek]

We'll have a look into the feasibility of this after we reach GA.

[baijum]

We'll have a look into the feasibility of this after we reach GA.

Thanks @theunrepentantgeek

To get a better picture of the end-user experience, I have created POC: https://www.youtube.com/watch?v=wjwxXSqpYHQ

The code is here: https://github.com/baijum/azure-service-operator/tree/provisioned-service The application and the other configurations are here: https://github.com/redhat-developer/openshift-app-services-demos/tree/main/samples/sbo/azure-provisioned-service-poc

[matthchr]

This is still something we might be interested in, but haven't seen a lot of user requests yet so it's not high priority.

[matthchr]

No change from above

[matthchr]

No change from above.

[theunrepentantgeek]

Still somewhat interested.