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

Unable to Fetch Helm Chart from Self-hosted ChartMuseum Registry #5686

Open
Piwero opened this issue May 1, 2024 · 1 comment
Open

Unable to Fetch Helm Chart from Self-hosted ChartMuseum Registry #5686

Piwero opened this issue May 1, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@Piwero
Copy link

Piwero commented May 1, 2024

What happened?

When attempting to use a Helm chart from a self-hosted ChartMuseum registry with basic authentication through kustomize, the following error occurs:

Error: Error: looks like "https://mychartmuseumrepo.com" is not a valid chart repository or cannot be reached: failed to fetch https://mychartmuseumrepo.com/index.yaml : 401 Unauthorized
: unable to run: 'helm pull --untar --untardir apps/base/chartmuseum/charts/mywantedchart-0.0.1 --repo https://mychartmuseumrepo.com/ mywantedchart --version 0.0.1' with env=[HELM_CONFIG_HOME=/var/folders/xxxx/helm HELM_CACHE_HOME=/var/folders/f8/xxxx/helm/.cache HELM_DATA_HOME=/var/folders/f8/xxx/helm/.data] (is 'helm' installed?): exit status 1

What did you expect to happen?

I expected kustomize to successfully fetch the Helm chart from the self-hosted ChartMuseum registry using the provided basic authentication credentials.

How can we reproduce it (as minimally and precisely as possible)?

To reproduce the issue:

  1. Set up a self-hosted ChartMuseum registry requiring basic authentication and push mywantedchart to it

  2. Add the ChartMuseum repository to Helm using the command: helm repo add mychartmuseumrepo https://mychartmuseumrepo.com -u myuser -p mypassword.

  3. Create a kustomization.yaml file with the following content:

helmCharts:
- name: mywantedchart
  repo: https://mychartmuseumrepo.com
  releaseName: chartmusesum
  version: 0.0.1
  valuesFile: values.yaml 
  1. Run kustomize build . --enable-helm.

Expected output

Kustomize should successfully fetch the Helm chart from the specified repository using the provided authentication credentials.

Actual output

Kustomize fails to fetch the Helm chart from the repository and returns a 401 Unauthorized error.

Error: Error: looks like "https://mychartmuseumrepo.com" is not a valid chart repository or cannot be reached: failed to fetch https://mychartmuseumrepo.com/index.yaml : 401 Unauthorized
: unable to run: 'helm pull --untar --untardir apps/base/chartmuseum/charts/mywantedchart-0.0.1 --repo https://mychartmuseumrepo.com/ mywantedchart --version 0.0.1' with env=[HELM_CONFIG_HOME=/var/folders/xxxx/helm HELM_CACHE_HOME=/var/folders/f8/xxxx/helm/.cache HELM_DATA_HOME=/var/folders/f8/xxx/helm/.data] (is 'helm' installed?): exit status 1

Kustomize version

v5.4.1

Operating system

MacOS

@Piwero Piwero added the kind/bug Categorizes issue or PR as related to a bug. label May 1, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label May 1, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants