For a Digital Access system, the following different deployment options are available:
Even if Digital Access component is available as Docker images, it can still be deployed as virtual appliance. The big difference to older version is, that the virtual appliance will be used as the Docker host that runs the Docker containers of the Digital Access component services inside it.
Once the virtual appliance is deployed, upgrades will only apply to the Docker containers inside but not the appliance itself. This has the advantage that changes made inside the appliance will remain, even after an upgrade of Digital Access component.
Instructions on how to deploy Digital Access component as virtual appliance can be found here.
This deployment option is still in beta status. It should not be used for productive environments.
All Digital Access component services, such as administration service and policy service, are available as Docker images. An additional image, called Orchestrator, is used to maintain all other services. This includes pulling, starting and stopping, as well as upgrading.
To deploy Digital Access component with Docker, only the Orchestrator image needs to be pulled and configured. Instructions on how to do it can be found here.
A Kubernetes deployment for Digital Access component will be available later.