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

Support native handling of multiple private OCI registries within ArgoCD.

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • GitOps
    • False
    • None
    • False
    • Not Selected

        • What is the nature and description of the request?*

      Client is creating an ArgoCD application with a kustomization file through an ArgoCD ApplicationSet. They are facing Authentication error for ArgoCD kustomization helmchart with private OCI repository using  Azure Container registry.

        • Why does the customer need this? (List the business requirements here)*

      Security and Stability Risks: Manual interventions in the filesystem of a running container go against best practices for containerized environments, potentially compromising security and stability.
      Lack of Persistence: Such changes are ephemeral and do not survive pod restarts, leading to additional maintenance overhead and potential downtime.
      Scalability Concerns: For organizations utilizing multiple private OCI registries, managing individual configurations and credentials for each is neither scalable nor practical.
      Credential Management: The reliance on continuously refreshing credentials, especially in environments like AWS ECR where tokens expire frequently, adds unnecessary complexity and potential points of failure.

       

        • Customer needs a solution that:* 

      Supports native handling of multiple private OCI registries within ArgoCD.
      Automates credential management, potentially integrating with cloud-native solutions like AWS IAM roles and IRSA, or equivalent in other cloud environments.

       

       

              halawren@redhat.com Harriet Lawrence
              rhn-support-dtambat Darshan Tambat
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: