Bug 1807584 - Helm Topology groups doesn't work for Helm 3 charts
Summary: Helm Topology groups doesn't work for Helm 3 charts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.5.0
Assignee: Rohit Rai
QA Contact: Gajanan More
URL:
Whiteboard:
Depends On:
Blocks: 1807585
TreeView+ depends on / blocked
 
Reported: 2020-02-26 16:30 UTC by Rohit Rai
Modified: 2020-07-13 17:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1807585 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:21:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Groups of helm 3 charts (150.28 KB, image/png)
2020-03-10 09:07 UTC, Gajanan More
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:22:05 UTC

Description Rohit Rai 2020-02-26 16:30:04 UTC
Description of problem:
Helm Topology groups rely on labels to identify all the resources created by helm release. This strategy doesn't work for Helm 3 charts since they do not have all the labels.

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


How reproducible:
Always

Steps to Reproduce:
1. Install bitnami/redis chart.
2. Go to topology

Actual results:
Resources created by Helm release are not grouped together.

Expected results:
All the resources created by helm release should be grouped together.

Additional info:

Comment 3 Gajanan More 2020-03-10 09:07:37 UTC
Created attachment 1668832 [details]
Groups of helm 3  charts

Comment 4 Gajanan More 2020-03-10 09:08:50 UTC
I have validated this bug on 
Build: 4.5.0-0.ci-2020-03-10-023720
Browser: Google Chrome 78.0.3904.108
Marking this bug as verified.

Comment 6 errata-xmlrpc 2020-07-13 17:21:31 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.