Bug 1861800

Summary:	ACM Lifecycle should not display ArgoCD applications
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	Gerald Nunn <gnunn>
Component:	App Lifecycle	Assignee:	Feng Xiang <fxiang>
Status:	CLOSED ERRATA	QA Contact:	Eveline Cai <ecai>
Severity:	medium	Docs Contact:	bswope <bswope>
Priority:	unspecified
Version:	rhacm-2.0	CC:	gghezzo, xiangli
Target Milestone:	---	Flags:	gghezzo: rhacm-2.1+
Target Release:	rhacm-2.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-05 11:55:17 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:
Embargoed:

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