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

Feature-Request: Possibility to specify Proxy in ArgoCD custom resource

XMLWordPrintable

    • 8
    • False
    • False
    • Undefined

      1. Proposed title of this feature request
      Feature-Request: Possibility to specify Proxy in ArgoCD custom resource

      2. What is the nature and description of the request?
      In multitenant environment it's possible and likely that different proxies may be used to access Source Repositories (as potentially different tenant have different proxies in use). Currently only the OpenShift Container Platform - Cluster Wide proxy can and will be used. But since this may not necessarily apply to user workloads in different tenants it's required to be able and specify a proxy per ArgoCD custom resource. That way, tenant can specify it's required proxy and even modify/adjust that on instance level and therefore leverage different proxies if required.

      3. Why does the customer need this? (List the business requirements here)
      In multitenant environment it may not be the goal to use the OpenShift Container Platform - Cluster Wide proxy but rather have a tenant specific proxy configured when working with upstream source repositories. Therefore it's required to be able and specify a proxy on per ArgoCD instance level

      4. List any affected packages or components.
      OpenShift GitOps

              Unassigned Unassigned
              rhn-support-sreber Simon Reber
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: