Collect and document implementors of the Provided Service Duck Type

[nebhale]

Collect and document implementors of the Provided Service duck type.

[arthurdm]

One implementor we're interested in is Strimzi. @AndrewJSchofield had started a proposal, which we should update to be a duck type if possible.

[baijum]

Created a feature request to MongoDB: https://feedback.mongodb.com/forums/924355-ops-tools/suggestions/44030625-support-service-binding-specification-for-kubernet

[baijum]

Created a feature request to Redis: RedisLabs/redis-enterprise-k8s-docs#186

[nebhale]

@arthurdm and @baijum Are you aware of any implementors yet? I've got one on my side and want to make sure any that have been successfully implemented are included.

[arthurdm]

I know that both of the Runtime Component Operator and Open Liberty Operator teams are aiming for an update this month to be able to expose a workload (app) as a bindable service endpoint via the duck type. Will need to circle back on this.

[arthurdm]

@nebhale - Here's the relevant doc for the Runtime Component Operator: https://github.com/application-stacks/runtime-component-operator/blob/main/doc/user-guide-v1beta2.adoc#exposing-runtimecomponent-applications-as-provisioned-services

This is also applicable to the Open Liberty Operator, since it builds from the Runtime Component Operator library.

[arthurdm]

Here's the link to the Open Liberty Operator: https://github.com/OpenLiberty/open-liberty-operator/blob/main/doc/readme.adoc

hi @leochr - do you know when RCO and OLO will support the v1 of the spec?

[leochr]

Hi @arthurdm, RCO and OLO releases are planned for 3Q. The new WebSphere Liberty Operator will also support the v1 spec and it'll be released in 2Q.