The following section details the options for uploading BlueCat Gateway images to BlueCat DNS/DHCP Servers.
Uploading BlueCat Gateway images for BlueCat DNS/DHCP Servers that are unable to access respositories
New in Integrity 9.5, users can upload Gateway images to DNS/DHCP Servers through the Address Manager user interface. On a device with repository access, pull the Gateway image from the repository and save it to a tar archive. Once you have created the tar or tar.gz file, refer to Configuring Gateway service on a DNS/DHCP Server to upload the Gateway image and enable the service.
Uploading custom BlueCat Gateway images for deployment to production environment
A custom image is BlueCat's recommended best practice for deploying Gateway to a production environment. A custom image is built on top of the Gateway base image. The deployed container will include all necessary workflow/application data, thereby removing the need to import workflows or change configurations of a running container manually. This simplifies deployments to Production and improves container resiliency. For more information on the Built-in Workspace, and using Dockerfile to generate custom images, refer to Adding Built-in Workflows to the Container in the BlueCat Gateway Administration Guide.
Before you begin, ensure you have completed the following:
- Ensure Gateway Service is disabled on the production BDDS
- The custom image has been built on BlueCat Gateway v20.12.1 or greater and leverages the Built-in workspace. For more information on the Built-in Workspace and using Dockerfile to generate custom images, refer to Adding Built-in Workflows to the Container
- The custom image has been packaged into a tar file:
docker save –o /path/to/file.tar <repository|imagename>