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

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

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Helm
    • False
    • False
    • Undefined
    • HELM-75Deliver Enterprise Ready Package Management

      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.
      https://helm.sh/docs/helm/helm_repo_add/

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

      spec:
      connectionConfig:
      username: username
      password:
      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

            slemeur@redhat.com Stevan Le Meur
            rhn-support-vkochuku Vinu Kochukuttan
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: