EPIC Goal

The ArgoCD plugin needs to support more than one Argo instance and namespace per component. A component may need to be deployed to different clusters depending where it is in the lifecycle (dev/test/stage/prod/etc) and RHDH needs to be able to properly interact with them.

Background/Feature Origin

Customers often deploy through different environments (e.g., dev, staging, production) that might reside on different systems, which we can't handle well today. 

Why is this important?

So customers can see deployment statuses from all their environments, not just one hardcoded environment, so it aligns with how they work in production settings, not just PoCs.

User Scenarios

• As an admin, I want to be able to configure multiple Argo instances per component for ArgoCD plugin so that I can view them in RHDH
• As an admin, I want to be able to configure multiple namespaces where Argo apps are deployed.
• Stretch: As a user, I want to view all ArgoCD instances that fulfill app-selector annotation + other specified annotations, even if ArgoCD namespace and instance is not specified in annotations for the component.

Dependencies (internal and external)

Acceptance Criteria

• ArgoCD plugin supports multiple ArgoCD instances and namespaces per component
  • Admins can specify multiple values for annotations of 
    argocd/instance-name and argocd/app-namespace, separated by comma
  • Stretch: When no instance or namespace is specified, default is to check all instances to align with Roadie's functionality. Current functionality is to use the first ArgoCD instance specified.
  • if possible, it should present in order that they are defined in the config, where first defined cluster means those are the left-most or top.
• New functionality works correctly also when only ArgoCD frontend plugin is used.
• Connections to the ArgoCD instances should be secured with authentication.