Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-5016

Argo Agent: Integration into Red Hat productization

XMLWordPrintable

    • Argo Agent: Integration into Red Hat productization
    • False
    • Hide

      None

      Show
      None
    • False
    • Done
    • SECFLOWOTL-153 - Argo Agent: Integration into Red Hat productization
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      In this release, we are releasing Argo CD agent in Technical Preview. We have productized container image of the Argo CD agent along with the custom property in ArgoCD custom resource to enable the principal component in the hub cluster. For more information on how to install and configure the Argo CD agent in a multi-cluster setup, please refer the upstream documentation available here -> https://github.com/argoproj-labs/argocd-agent/blob/main/docs/getting-started/openshift/index.md and also https://argocd-agent.readthedocs.io/latest/getting-started/openshift/
      Show
      In this release, we are releasing Argo CD agent in Technical Preview. We have productized container image of the Argo CD agent along with the custom property in ArgoCD custom resource to enable the principal component in the hub cluster. For more information on how to install and configure the Argo CD agent in a multi-cluster setup, please refer the upstream documentation available here -> https://github.com/argoproj-labs/argocd-agent/blob/main/docs/getting-started/openshift/index.md and also https://argocd-agent.readthedocs.io/latest/getting-started/openshift/
    • Feature
    • Proposed

      Epic Goal

      • See parent Jira for details
      • Note - the first productization iteration is with CPaaS as konflux is not adopted by the team yet.

      Why is this important?

      • …

      Scenarios

      1. ...

      Acceptance Criteria (Mandatory)

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …
      •  

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

              nmirasch@redhat.com Neus Miras Chueca
              rh-ee-anjoseph Anand Francis Joseph
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: