Description of problem: A breaking change was introduced in the Service Binding Request CRD in order to support multiple backing selectors. `backingServiceSelector` and `backingServiceSelectors` are both optional. In the past `backingServiceSelector` was required. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Install the Service Binding Operator 2. Create a deployment named 'my-app' 3. Create a service binding request without any backing service selectors: apiVersion: apps.openshift.io/v1alpha1 kind: ServiceBindingRequest metadata: name: binding-1 spec: applicationSelector: group: apps resource: deployments resourceRef: my-app version: v1 detectBindingResources: true 4. Visit topology Actual results: White screens with error `Uncaught TypeError: Cannot read property 'kind' of undefined` Expected results: Topology to load correctly. Additional info:
I have validated the bugzilla on: Build: 4.5.0-0.nightly-2020-06-05-214616 Browser: Google Chrome Version 81.0.4044.129 Marking this as verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409