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

Enable Argocd to connect to argocd redis instance from another cluster

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • Enable Argocd to connect to argocd redis instance from another cluster
    • False
    • None
    • False
    • To Do

      Epic Goal

      Argocd Instance should be able to connect to other argocd instance redis instance running on a different k8s/openshift cluster. Having a shared redis instance will reduce the delay in accessing the application status and other features from UI or CLI. 

      Why is this important?

      • By sharing Argocd Redis instance with another Argocd instance running on a different cluster, argocd-agent will be able to take advantage of caching.

      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):

      Open questions::

      •  

      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

              Unassigned Unassigned
              rh-ee-ansingh Anand Singh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: