Air-gapped installations
In scenarios where the environment in which EDA is being deployed does not have any connectivity to the Internet, a local mirror with all the resources EDA needs, must be deployed.
Air-gapped environments
In an air-gapped environment, an Assets VM is deployed to provide the services that serve the container images, git repositories and artifacts used during installation of the EDA Talos Kubernetes cluster and EDA itself.
The goal of the air-gapped solution design is to allow flexibility in the deployment and content of the Assets VM in the air-gapped environment. By providing a standalone Assets VM without any assets automatically included, there is freedom of choice of what assets are uploaded to the Assets VM. It allows for a single Assets VM to be used for multiple deployments and versions of EDA, as the assets for multiple versions of EDA can be uploaded to the same Assets VM.
Similarly, by splitting up the assets in bundles, it is possible to only upload specific content to the Assets VM. The bundle concept also allows for the creation of custom bundles, such as for third-party apps, so they can also be hosted on the Assets VM.
Public and air-gapped systems
- public environment - an environment that has Internet access. You use a system with Internet access to create the Assets VM image and to download all the necessary assets and tools.
- air-gapped environment - the system that does not have Internet access. This is the environment in which EDA is deployed.
For each environment, you must have a system from where you can execute the steps. This system can be the same system that you used to first connect to the Internet, follow the steps for the public network, and then move the system to the air-gapped environment to continue.
You can also have two systems, where you copy the data from the public system to the air-gapped system.