To make Operators more easily bind-able by Service Binding Operator - Define OLM descriptor format (for Operator authors) for expressing what is relevant for binding

How does an operator author express what is interesting for applications ?

The operator author would specify that in the OLM Descriptors.

A Cassandra CR’s status/spec might 50 fields, but not all of them would be interesting! Could we use that.

 specDescriptors:
     - description: The name of the secret object that stores the admin credentials.
       displayName: Auth Secret
       path: authSecret
      *  bindable: true*
       x-descriptors:
       - urn:alm:descriptor:io.kubernetes:Secret
     - description: The name of the secret object that stores the server's TLS
         certificate.
       displayName: Server TLS Secret
       path: tls.static.member.serverSecret
       x-descriptors:
       - urn:alm:descriptor:io.kubernetes:Secret
 

The descriptors could specify that specific fields are interesting for applications to bind to.

Also, descriptors could optionally point to secrets because some operator authors wouldn’t be comfortable dumping passwords into a CR status?

Action item:
Involve evan, operator-sdk and start defining the format

Acceptance criteria

• define the format
• modify an existing operator to use this format.