[doc] 14 Setting Up a Registry for an Air Gapped Environment - needs to be synched with the CaaSP v4 Air Gap setup

[Martin-Weiss]

14 Setting Up a Registry for an Air Gapped Environment

https://documentation.suse.com/suse-cap/1.5.1/single-html/cap-guides/#cha-cap-depl-air-gap-registry

It seems that this is somewhat outdated. In CaaSP v4 we use registries.conf for mapping and we use skopeo to copy images. We use a txt file which is part of the documentation to have the list of images requres.

[btat]

Since this is about the script's implementation details, I will defer to @jandubois (who wrote the script) on how to proceed.

[jandubois]

It may be possible that there is a better way to handle this in CaaSP, but the documentation is supposed to be generic for any k8s install.

I have no idea how the CaaSP mechanism works, and can't look into this until after CAP-1.5.2 ships. Maybe the CaaSP team can point us to documentation how this should be set up?

[Martin-Weiss]

IMO we really need a standard SUSE way for this. All our products have the same challenge for Airgap where we need a replication and staging mechanism and an on premise registry. It does not make much sense if every "silo" re-invents the wheel - especially in case CaaSP is the basis for CAP and where the Airgap management of helm charts and images needs to be aligned at the customer side ;-). In the future also SES will have the same challenge - so maybe we should start an initiative for a general SUSE solution?

As reference - here the CaaSP Airgap story https://susedoc.github.io/doc-caasp/master/caasp-deployment/single-html/#_airgapped_deployment (also work in progress as this also needs adjustments..)

[btat]

Marking as blocked. Pending validation from engineering.