Bug 1936801 - Support ServiceBinding 0.5.0+
Summary: Support ServiceBinding 0.5.0+
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Sahil Budhwar
QA Contact: Gajanan More
Depends On:
Blocks: 1936803
TreeView+ depends on / blocked
Reported: 2021-03-09 08:17 UTC by Sahil Budhwar
Modified: 2021-07-27 22:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-07-27 22:51:56 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:52:20 UTC

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


Note You need to log in before you can comment on or make changes to this bug.