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

Question for --allow-overwrite #33

Closed
yongzhang opened this issue Jan 29, 2018 · 2 comments
Closed

Question for --allow-overwrite #33

yongzhang opened this issue Jan 29, 2018 · 2 comments

Comments

@yongzhang
Copy link

Hi,

I'm not sure my question is regarding chart repo or chartmuseum, is it allow to store multiple versions of a chart? For example, I have a chart named nginx, I uploaded version 1.0.0 and 1.0.1, should I see both versions by helm search? Actually, I used --allow-overwrite parameter for chartmuseum, I can see chart 1.0.0.tgz and 1.0.1.tgz were both in the chart storage, but can only see version 1.0.1 by helm search, means only 1.0.1 in index.yaml, is this the expected behavior?

@jdolitsky
Copy link
Contributor

@hiscal2015 this is a question about Helm, but more than happy to help out.

You can certainly store multiple versions of a chart in a repository. In order to see all versions of a chart, use the -l flag when searching, for example helm search stable/mysql -l. If you look at index.yaml you should see both versions.

ChartMuseum's --allow-overwrite flag will allow you to re-upload a chart of the same version. For example, if chart-1.0.1.tgz has already been uploaded, you will be able to upload chart-1.0.1.tgz
again without error, replacing the one in storage. Without the flag, you will receive an error that the version already exists.

Hope this helps!

@yongzhang
Copy link
Author

@jdolitsky Thank you very much, it helps a lot!

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

No branches or pull requests

2 participants