Architecture

The On-Premise solution contains multiple components that require pre-configured infrastructure to operate. The solution is designed in such a way that most of the services and infrastructure can be installed in an isolated local network with limited or no internet access.

Internet access is required by:

• The DGCLI utility in the license or pull modes.
• The Traffic API Proxy. The service is hosted in a private network, but a firewall or a load balancer needs to be configured to allow the Traffic API Proxy to access the internet.

The diagrams below show the architecture of component interactions in two scenarios: with internet access and without internet access.

With internet access

How the solution works:

1. DGCLI downloads installation artifacts from Urbi public update servers:

   • data sets required to install or update services
   • Docker images of services

2. DGCLI places the datasets into S3 compatible storage (Object Storage on the diagram) and Docker images into the Docker registry (Image Storage on the diagram), both located in the private network.

3. The internal Kubernetes cluster uses these artifacts:

   • Docker images are delivered directly to their corresponding services located in the Kubernetes cluster
   • Helm charts use the downloaded datasets for installing and updating services

4. The service or its new version becomes available to end users.

Without internet access

How the solution works:

1. DGCLI downloads installation artifacts from Urbi public update servers:

   • data sets required to install or update services
   • Docker images of services

2. The artifacts are saved to the file system (flash drive, external drive, or other storage media) (File System on the diagram) and transferred to the private network without internet access.

3. In the private network, DGCLI uploads the datasets from the file system into S3 compatible storage (Object Storage on the diagram) and Docker images into the Docker registry (Image Storage on the diagram).

4. The internal Kubernetes cluster uses these artifacts:

   • Docker images are delivered directly to their corresponding services located in the Kubernetes cluster
   • Helm charts use the downloaded datasets for installing and updating services

5. The service or its new version becomes available to end users.

For more information on downloading installation artifacts, see the Preparation for installation section.