Bug 1833142 - Kibana CR created by CLO should match Elasticsearch CR pattern
Summary: Kibana CR created by CLO should match Elasticsearch CR pattern
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
urgent
low
Target Milestone: ---
: 4.5.0
Assignee: ewolinet
QA Contact: Qiaoling Tang
URL:
Whiteboard:
Depends On:
Blocks: 1833611
TreeView+ depends on / blocked
 
Reported: 2020-05-07 21:38 UTC by ewolinet
Modified: 2020-07-13 17:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:35:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 508 0 None closed Bug 1833142: Renamed kibana CR instance 2020-11-02 14:52:37 UTC
Github openshift elasticsearch-operator pull 348 0 None closed Bug 1833142: Renamed kibana CR instance 2020-11-02 14:52:38 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:36:19 UTC

Description ewolinet 2020-05-07 21:38:32 UTC 
Description of problem:
Currently the Kibana CR is created as "instance" which differs from the current pattern that Elasticsearch uses which is "elasticsearch".

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

How reproducible:
always

Actual results:
Kibana CR is created as "instance"

Expected results:
Kibana CR is created as "kibana"
Comment 4 Qiaoling Tang 2020-05-12 07:08:34 UTC 
Verified with images from 4.5.0-0.ci-2020-05-11-212141

$ oc get kibana
NAME     AGE
kibana   4s
Comment 5 errata-xmlrpc 2020-07-13 17:35: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.