Bug 1834805 - Support kafkasource new spec changes from UI
Summary: Support kafkasource new spec changes from UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.5
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: 4.5.0
Assignee: Karthik Jeeyar
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-12 13:12 UTC by Karthik Jeeyar
Modified: 2020-07-13 17:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:37:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 5407 0 None closed Bug 1834805: Support new spec changes in kafkasource 2020-10-01 16:17:52 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:38:13 UTC

Description Karthik Jeeyar 2020-05-12 13:12:34 UTC
Description of problem:


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

How reproducible:
Always

Steps to Reproduce:
1. Install openshift serverless operator
2. On Add page, click on the event source
3. choose kafkasource and fill the form

Actual results:
The existing UI will accept only one string field

Expected results:
As per the new API changes in v1alpha1 API, it should accept array of strings.
https://github.com/knative/eventing-contrib/tree/master/kafka/source

Comment 3 Gajanan More 2020-05-26 08:39:16 UTC
I have validated the bugzilla on
Build: 4.5.0-0.nightly-2020-05-25-232952
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified

Comment 4 errata-xmlrpc 2020-07-13 17:37:59 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:2409


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