Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-24682

Helm repositories require the packages to be relative to the index.yaml

    XMLWordPrintable

    Details

    • Notability:
      3

      Description

      When using a helm proxy, the URLs within the index.yaml are re-written to be relative to the location of the index.yaml.

      This is usually fine as it is the general case. However, in some cases the index.yaml is on a different server, and this is perfectly valid according to https://helm.sh/docs/topics/chart_repository/

       

      It is not required that a chart package be located on the same server as the index.yaml file. However, doing so is often the easiest.

       

      As a more concrete example, the index.yaml for ingress-nginx is here: https://kubernetes.github.io/ingress-nginx/index.yaml

      However, the packages within the index.yaml are under a different location and a relative path will not work: https://github.com/kubernetes/ingress-nginx/releases/download/ingress-nginx-2.11.0/ingress-nginx-2.11.0.tgz

      Note how kubernetes.github.io is not the same as github.com/kubernetes

      It should be possible for Nexus to map the URLs as necessary such that all subsequent requests go through the repository but to the correct endpoint.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              aishchenko Artem Ishchenko
              Reporter:
              mkearns Michael Kearns
              CC:
              Nick Toone
              Last Updated By:
              Nicolas Guilmeau
              Team:
              NXRM - Trinity
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title

                    PagerDuty