You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking for a tool that could help me easily analyze, export all artifacts from a helm, together with all images used, and then import to a desired (private) registry. This is a very common use case when we work with airgapped env.
Unfortunately, I couldn't find one that could best fit into such simple use case.
So I built an incomplete tool for fun: https://github.com/brightzheng100/helm-packager, which is a toy tool and is far away from complete.
I think your tool is a good starting point and I'd suggest to have sub commands, instead of a giant command with configuration file.
For example:
# 1. To export the Helm Charts and their sub Charts to be a local gz file
helmper export [-c <config file>] [-f <exported gz file>] [--dry-run]
# 2. To import the exported gz file to a registry
helmper import [-c <config file>] [-f <exported gz file>] [--dry-run]
# 3. Copy the Helm Charts and their sub Charts to the desired registry -- this is what current helmper does# But with the --dry-run flag, we can analyze the Helm Charts and their sub Charts without coping the actual artifacts
helmper copy [-c <config file>] [--dry-run]
The text was updated successfully, but these errors were encountered:
I am interested in having a folder with a helm folder (in a git repo) and the use helmper to package that Chart from the folder and push it to oci registry (harbor). Is this relevant to this issue? (eg. is this the issue I should be watching? :) )
Thank you!
I was looking for a tool that could help me easily analyze, export all artifacts from a helm, together with all images used, and then import to a desired (private) registry. This is a very common use case when we work with airgapped env.
Unfortunately, I couldn't find one that could best fit into such simple use case.
So I built an incomplete tool for fun: https://github.com/brightzheng100/helm-packager, which is a toy tool and is far away from complete.
I think your tool is a good starting point and I'd suggest to have sub commands, instead of a giant command with configuration file.
For example:
The text was updated successfully, but these errors were encountered: