Uploaded image for project: 'Helm'
  1. Helm
  2. HELM-219

Basic authentication for ProjectHelm Chart repository in helmchartrepositories.helm.openshift.io CRD.


    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Normal Normal
    • 4.12
    • None
    • Helm
    • Basic authentication support for Helm repositories
    • False
    • False
    • To Do
    • HELM-75Deliver Enterprise Ready Package Management
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined

      1. Proposed title of this feature request
      Basic authentication for Helm Chart repository in helmchartrepositories.helm.openshift.io CRD.

      2. What is the nature and description of the request?
      As of v4.6.9, the HelmChartRepository CRD only supports client TLS authentication through spec.connectionConfig.tlsClientConfig.

      3. Why do you need this? (List the business requirements here)
      Basic authentication is widely used by many chart repositories managers (Nexus OSS, Artifactory, etc.)
      Helm CLI also supports them with the helm repo add command.

      4. How would you like to achieve this? (List the functional requirements here)
      Probably by extending the CRD:

      username: username
      secretName: secret-name

      The secret namespace should be openshift-config to align with the tlsClientConfig behavior.

      5. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
      Trying to pull helm charts from remote private chart repositories that has disabled anonymous access and offers basic authentication.
      E.g.: https://github.com/sonatype/docker-nexus

            isuttonl Igor Sutton (Inactive)
            slemeur@redhat.com Stevan Le Meur
            0 Vote for this issue
            3 Start watching this issue