Chart tarball

[p1-repo-sync-bot[bot]]

Feature Request

Why

Currently, the only way to import Big Bang charts (https://registry1.dso.mil/harbor/projects/133/repositories) into an airgapped enironment is to either scrape them from Harbor or manually download each chart. This is time consuming and the manual collection sometimes results in missing charts due to human error.

Proposed Solution

Provide a charts.tar.gz file similar to the git repositories (repositiories.tar.gz) and images (images.tar.gz) as a single file that can be pulled from S3 and imported into an airgapped environment.

[p1-repo-sync-bot[bot]]

bb8-bot commented:

---

@ppryde this issue has been inactive for 30 days and is being labelled as ~stale. If this issue is still required please take action by removing the ~stale label and commenting with an update, status, or justification. If this issue is not required please close it or label it as ~delete-me. If no action is taken this issue will be auto closed in 60 days.

[p1-repo-sync-bot[bot]]

Issue 'Chart tarball' closed from GitLab side

[p1-repo-sync-bot[bot]]

noahbirrer commented:

---

Hi @ppryde, we have some documentation available regarding BigBang deployment into airgapped environments. Currently these guides are experimental, so your experience may vary.

The repositories.tar.gz artifact includes the BigBang repository itself and repositories for all packages within BigBang. This artifact can be imported to a git server in your environment by following these steps.

If you simply need a tarball for each chart, you can follow these steps:

• After extracting repositories.tar.gz, you will find a directory for each package.
• cd into package directory and run git checkout
• Run helm package chart to create a tarball for the chart

Another option is to use zarf for managing BigBang releases in airgapped environments.

Feel free to raise this issue again if none of the outlined solutions work for your use case.

[p1-repo-sync-bot[bot]]

ppryde commented:

---

Thanks for the information. What we've been doing now is using the oci_package_list.txt to build a manifest to pull the charts from registry1, adding the bigbang chart, then tar'ing them up and shipping that file. It has been working for us without having to keep importing git repos into the environment.