-
Notifications
You must be signed in to change notification settings - Fork 187
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
Report descriptive error for invalid chart repository URLs / index data #654
Comments
Hey, did you by any chance use a tab character when adding |
Hi aryan9600, i already check the tab character are in the yaml file. below result that is run 'set list' on the VIM.
|
The problem is likely that GitLab does not serve the expected You either need to figure out what the right URL is for static GitLab content (like As a rule of thumb for easy debugging: if |
We could be nicer (like the $ helm repo add foo https://example.com
Error: looks like "https://example.com" is not a valid chart repository or cannot be reached: failed to fetch https://example.com/index.yaml : 404 Not Found |
Thanks @hiddeco I was confused, the error message was happen by parsing the YAML. i did not think about the fetching the helm chart index.html. Also you suggest to improve the error message, right? Thanks for your kindly support. |
Hi,
I gonna use private helm chart repository that is working on GitLab CE.
So i made helmrepository and helmrelease following this guideline.
but as you can see, below error message printed for helmrepsitory resource that i made.
I already did run flux bootstrap and there is running the source-controller (ghcr.io/fluxcd/source-controller:v0.21.2) at the cluster.
You can check the YAML file that was used to create helmrepository.
I can not find what makes syntax error or invalid line.
if i applied upper YAML file without "secretRef" line, it succeed.
So i think the "secretRef" has something wrong, but I could not find any problem.
Can anyone give some advice or if this issue turn out to be error, please fix it.
The text was updated successfully, but these errors were encountered: