search

helm / chartmuseum

helm chart repository server
https://chartmuseum.com
Apache License 2.0
3.52k stars 396 forks source link

Can browse to default index.html, but "helm repo add" returns 404 #763

Closed sierrasoleil closed 2 months ago

sierrasoleil commented 2 months ago

I installed Chartmuseum in EKS via the helm chart. Everything appears to be working; no errors from the S3 connection, and I can browse to the default "Welcome to ChartMuseum!" page. However, helm repo add <repo-name> <repo-url> always fails with: Error: looks like "https://<repo-url>/" is not a valid chart repository or cannot be reached: failed to fetch https://<repo-url>/index.yaml : 404 Not Found

I can't find any issues with the ALB, Ingress or Service. I enabled debug logging, but the only entries in the pod logs are the health checks.

wmcnamee-coreweave commented 2 months ago

I just tried running this locally, and I'm also getting a 404 for http://localhost:8080/index.yaml

sierrasoleil commented 2 months ago

I just finished a series of support calls with AWS about EKS, and it turns out the 404s were coming from the Application Load Balancer, not from Chartmuseum itself. That is now fixed, and unfortunately the solution won't help you diagnose an issue with Chartmuseum on localhost.

For anyone who is interested, if you want a single wildcard path set in your ingress, it must be set to /* and not /. The ALB rules created by the AWS Load Balancer Controller will not see / as a prefix, and without the wildcard, anything that doesn't exactly match / will get back 404. This will not show up in the pod logs.