Describe what should be investigated or refactored
The purpose of Zarf packages should generally be complete portability to include airgapped environments as primary targets.
All example packages should be deployable offline but our testing structure does not include this as a requirement.
Zarf should support an additional workflow that:
- Step to build all of the example packages online + init package + binary and uses the upload action to store them
- Step that is hardened to remove all internet access (egress) that deploys each package to validate deployment success
A kubernetes runtime in this hardened step may also require an additional artifact pulled during the first step.
Additional context
Due to size of the runners - there may be constraints to bulding all of the examples up front.
Describe what should be investigated or refactored
The purpose of Zarf packages should generally be complete portability to include airgapped environments as primary targets.
All example packages should be deployable offline but our testing structure does not include this as a requirement.
Zarf should support an additional workflow that:
A kubernetes runtime in this hardened step may also require an additional artifact pulled during the first step.
Additional context
Due to size of the runners - there may be constraints to bulding all of the examples up front.