Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-7954

Integrate native support for Argo Workflows within OpenShift GitOps

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • openshift-4.16, openshift-4.18, openshift-4.19
    • GitOps
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request
      Integrate native support for Argo Workflows within OpenShift GitOps

      2. What is the nature and description of the request?
      We would like to request RedHat to integrate native support for Argo Workflows within OpenShift GitOps. This integration would enable orchestration of complex day2 operations, improve automation, and align with our GitOps strategy already built around ArgoCD.

      3. Why does the customer need this? (List the business requirements here)
      Background and Current State
      We have adopted openshift gitops as a core component for our day2 operations. It is used for GitOps-based application deployment. However, OpenShift GitOps currently lacks native support for Argo Workflows, requiring custom integrations and extra efforts to manage the dependency between the diffrerent components.

      Problem Statement
      The absence of native Argo Workflows support in OpenShift GitOps leads to:
      Increased operational overhead for maintaining custom operations.
      lack of visibility and traceability across deployment workflows.
      Inconsistent user experience across teams and environments.

      Proposed Enhancement
      We propose that Redhat integrate Argo Workflows within OpenShift GitOps.
      Provide lifecycle management, RBAC, and observability for workflows.
      Offer CRD support and UI integration within the OpenShift/gitops console.

      Benefits

      • Operational Efficiency: Streamlined deployment pipelines with fewer manual steps.
      • Consistency: Unified GitOps experience across deployment and workflow orchestration.
      • Scalability: Better support for multi-cluster, multi-tenant environments.
      • Security & Compliance: Improved auditability and policy enforcement through centralized workflow management.

      Implementation Considerations
      Collaboration with RedHat engineering teams.
      Pilot integration in a non-production OpenShift cluster.
      Feedback loop via RedHat’s customer portal and TAM engagement.

      4. List any affected packages or components.
      GitOps operators

              halawren@redhat.com Harriet Lawrence
              rh-support-fgrosjea Franck Grosjean
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved:
                None
                None