Bug 1798288

Summary: Service binding should be through Knative Service
Product: OpenShift Container Platform Reporter: Jaivardhan Kumar <jakumar>
Component: Dev ConsoleAssignee: Jaivardhan Kumar <jakumar>
Status: CLOSED ERRATA QA Contact: Ruchir Garg <rgarg>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.3.0CC: aos-bugs, gamore, nmukherj
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Service binding request in topology is associated with Revisions in topology view Consequence: no new revision will get the associated secrets Fix: SBR should go through knative service secrets would be injected and in turn new revisions would be created Result: SBR works as expected with Knative Service
Story Points: ---
Clone Of:
: 1808968 (view as bug list) Environment:
Last Closed: 2020-05-04 11:33:13 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:
Bug Depends On:    
Bug Blocks: 1808968    

Description Jaivardhan Kumar 2020-02-05 04:37:05 UTC
Description of problem:

Currently, on hover on Revisions, we show connector which can be dropped to an Operator backed service which in turn creates Service Binding Request which is incorrect sbr should be created via knative service and in turn revisions should be rolled out

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Install OpenShift Serverless operator
2. Create a knative service with DevConsole Add flow
3. Install Service binding operator
4. Install Postgress operator and create an instance of a database
5. Go topology view and hover on revisions under knative service, should show a connector and can be dropped to a database instance created above

Actual results:
Currently, on hover on Revisions, we show connector which can be dropped to an Operator backed service which in turn creates Service Binding Request.

Expected results:
Service Binding Request would be from knative Service i.e on hover for knative service show connector which can be dropped to an Operator backed service which in turn creates Service Binding Request and inject required info in service.

Comment 2 Gajanan More 2020-03-02 11:25:05 UTC
https://issues.redhat.com/browse/ODC-2791 verified by Sahil Budhwar

Comment 4 errata-xmlrpc 2020-05-04 11:33:13 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, 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:0581