Problem:

APPSVC-501 introduced singleton BindableKinds that reports what GVKs are bindable within a cluster. That list can be consumed by clients, but it has the following limitations:

• resources having binding annotations are not detected as bindable services, only those having annotations on CRD can be detected
• clients need to perform additional queries (knowing bindable GVKs) to find out what bindable services exist in a namespace

Goal:

Provide an easy way to client to discover all bindable services in a given namespace/cluster so that they can be discovered even using kubectl

Why is it important?

Better UX with standard CLIs

Use cases

1. As a non privileged user, I should be able to discover and view a list of bindable services i have access to which are installed outside of my namespace but inside this cluster
2. As a user, I can discover all services bindable but if I don’t have access, I want to be able to request permission

Acceptance criteria

A user should be able to get a list of bindable services with a simple

kubectl get bindableservices

Exploration

• k8s duck types
• knative duck typing
• https://groups.google.com/g/kubernetes-sig-api-machinery/c/S6BTVjIRTlM
• https://github.com/n3wscott/sugar
• https://github.com/n3wscott/demo-autodm