Bug 1861800 - ACM Lifecycle should not display ArgoCD applications
Summary: ACM Lifecycle should not display ArgoCD applications
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: App Lifecycle
Version: rhacm-2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: rhacm-2.1
Assignee: Feng Xiang
QA Contact: Eveline Cai
bswope@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-29 15:13 UTC by Gerald Nunn
Modified: 2021-04-09 17:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-05 11:55:17 UTC
Target Upstream Version:
Embargoed:
gghezzo: rhacm-2.1+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 4030 0 None None None 2020-09-22 02:05:59 UTC
Red Hat Product Errata RHEA-2020:4954 0 None None None 2020-11-05 11:55:36 UTC

Description Gerald Nunn 2020-07-29 15:13:38 UTC
Description of problem:

ARgoCD applications appear in the ACM user interface even though it has no capability to manage them. This is likely because ArgoCD also has an Application object though it is in a different API group, Application.argoproj.io, then what ACM uses.

This is confusing for the user and ACM should stop showing Argo applications unless we plan on doing some sort of integration between the two (which I'd love to see personally)

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

2.0.0

How reproducible:

Every time

Steps to Reproduce:
1. Deploy ArgoCD and ACM in the same hub cluster
2. Deploy some ArgoCD applications in the hub cluster
3. Check the ACM user interface to see they appear

Actual results:

ACM displays ArgoCD applications

Expected results:

ACM should not display ArgoCD applications

Additional info:

Comment 4 errata-xmlrpc 2020-11-05 11:55:17 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 (Red Hat Advanced Cluster Management for Kubernetes version 2.1 images), 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/RHEA-2020:4954


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