Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure syncing subcharts from different registries #147

Open
LP0101 opened this issue Feb 22, 2022 · 3 comments
Open

Failure syncing subcharts from different registries #147

LP0101 opened this issue Feb 22, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@LP0101
Copy link

LP0101 commented Feb 22, 2022

When trying to sync a chart with subcharts in a different remote registry, the sync fails with no chart name found.

For example, trying to sync kube-prometheus-stack, it fails copying grafana, which is stored in a separate repo.

Example config:

source:
  repo:
    kind: HARBOR
    url: https://prometheus-community.github.io/helm-charts
target:
  repoName: myrepo
  containerRegistry: k8s.container.registry.io
  containerRepository: repository/demo/k8s
  repo:
    kind: OCI
    url: https://<REDACTED>.azurecr.io/helm
    auth:
      username: "<REDACTED>"
      password: "<REDACTED>"
charts:
  - kube-prometheus-stack

When running charts-syncer sync, I get this:

0222 16:19:31.882577 101820 index.go:164] unable to load "kube-prometheus-stack-32.2.1" chart: invalid "grafana-6.21.5" chart dependency: getting grafana-6.21.5 from index file: no chart name found

With the same error for each version it tries to pull. This also happens with other charts with subcharts stored in different registries.

@Lex45x
Copy link

Lex45x commented Apr 22, 2022

+1
We need to be able to specify multiple source repos to solve this problem.

@jotadrilo jotadrilo added the enhancement New feature or request label May 10, 2022
@jotadrilo jotadrilo self-assigned this May 10, 2022
@jotadrilo
Copy link
Contributor

Hello @LP0101!

I am glad you discovered this bug. Sadly, we don't plan to add support for multiple source chart repositories at the moment.
However, we will be happy to review and discuss any possible implementation you can send as PR.

@chrissgyulev
Copy link

Hi all ! I have implemented a solution to this. I will open a PR in the next few hours.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants