Bug 1936801

Summary: Support ServiceBinding 0.5.0+
Product: OpenShift Container Platform Reporter: Sahil Budhwar <sbudhwar>
Component: Dev ConsoleAssignee: Sahil Budhwar <sbudhwar>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: high Docs Contact:
Priority: urgent    
Version: 4.8CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-27 22:51:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1936803    

Description Sahil Budhwar 2021-03-09 08:17:34 UTC
Description
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.

Acceptance Criteria
support service binding operator both in 0.4.0 and 0.5.0 versions

Comment 1 Gajanan More 2021-03-10 12:12:15 UTC
Marking this bug as done. Verification done on:

Build: 4.8.0-0.nightly-2021-03-10-053945

Browser: Google Chrome 87

Please have a look at shared screenshot

Comment 4 errata-xmlrpc 2021-07-27 22:51:56 UTC
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.

https://access.redhat.com/errata/RHSA-2021:2438