1. Proposed title of this feature request

Identify Resources Managed by Argo CD in OpenShift Console

2. What is the nature and description of the request?

Users often need to be able to identify that a resource is directly managed by Argo CD. For example, any changes they make to the resource may be automatically reverted by Argo CD which causes user confusion.

This RFE would enable the OpenShift Console to display a banner or flag for resources that are managed by Argo CD so that it is clear to users. These RFE would require two features to complete:

• For OpenShift GitOps there needs to be a way to provide a reliable and consistent way to identify the resources managed by Argo CD. While Argo CD supports a variety of tracking methods, either label or annotation or both, these are completely configurable there is no way AFAIK to integrate these with automation or the console in a reliable manner.

As a result the OpenShift GitOps team would need to provide some sort of consistent marker, potentially a label, that could be used by the console to identify these resources.

A challenge with this RFE is that many operators will copy labels and annotations from source CRs to objects they create potentially dilluting the value of this label. In an ideal way there would be a way to mark the resource in a way that avoids this issue.

• A feature for the OpenShift Console dependent on the GitOps feature. The console would consume the marker provided by the GitOps team to display a banner or flag indicating that this resource is being managed by Argo CD.

This would need to work across all resources including dynamic plugins, ideally plugin authors should not need to be aware of this capability and have to handle it directly.

• Ideally this feature would be somewhat neutral to OpenShift GitOps in that adding the marker might be useful to have resources managed by other operators flagged and displayed in the Console.

3. Why does the customer need this? (List the business requirements here)

This capability enables users to clearly understand a resource is being managed by Argo CD and any changes made to that resource in the OpenShift Console may be reverted. It helps users avoid confusion and understand resources are being managed in their clusters.  

4. List any affected packages or components.

OpenShift GitOps
OpenShift Console