APPSVC-809 introduced a change in ServiceBinding group API name. The name will be in use from version 0.5.0 that is about to be released in this sprint (APPSVC-830).
As a user, I would like to continue binding services from the console.
Although this is officially a breaking API change, the fact that we changed only API group name, makes it possible to support both the current API group (operators.coreos.com) and the new one (binding.operators.coreos.com). The console can check what service binding CRD is available in the cluster, and based on that use the appropriate group name in its requests.
support service binding operator both in 0.4.0 and 0.5.0 versions
Marking this bug as done. Verification done on:
Browser: Google Chrome 87
Please have a look at shared screenshot
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.