Uploaded image for project: 'Service Binding'
  1. Service Binding
  2. APPSVC-978

Improved discoverability of Bindable Services

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Service Binding, UI
    • Improved discoverability of Bindable Services
    • False
    • False
    • To Do
    • QE Needed, Docs Needed, TE Needed, Customer Facing
    • 20% To Do, 0% In Progress, 80% Done

      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

            Unassigned Unassigned
            pedjak@gmail.com Predrag Knezevic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: