If you are deploying GSS on a BDDS from an internal repository or local image, refer to Prerequisites: Uploading BlueCat Gateway images in the Address Manager Administration Guide.
- Log in to the Address Manager user interface.
- From the configuration drop-down menu, select a configuration.
- Select the Servers tab. Tabs remember the page you last worked on, so select the tab again to ensure you're on the Configuration information page.
- Under Servers, click the name of a BDDS. The Details tab for the server opens.
- Click the server name menu and select Service Configuration.
- From the Service Type drop-down menu, select BlueCat Gateway. Address Manager queries the server and returns the current values for the service settings.
- Under General Settings, set the following
parameters:
- Enable Gateway Service—select this check box to enable BlueCat Gateway service.
- Ports—enter a list of ports to configure for
GSS. Add port
4789:4789/udp
for the high-availability heartbeat communication. - Environment Variables—enter a list of environment variables to pull to a container during startup.
- Under Repository Settings, set the following
parameters:
- Repository—enter
quay.io/bluecat/gss
- Tag—enter
24.1
- Username—enter your username used for
docker login
. - Password—enter your encrypted password used
for
docker login
.
- Repository—enter
- Click Update.
After you click Update, Gateway Service initializes, pulls the images from the cloud or local repository, and initiates the container. Allow some time to register the configuration, after which Address Manager will redirect you to the Service Type dropdown menu page.
To confirm that the Gateway Service and container are running, select BlueCat Gateway from the Service Type dropdown menu. At the bottom of the page, you can find the Status and Description fields. If the Status displays RUNNING, the Gateway Service is enabled and the container is running.
Attention: A known issue exists where the Status may display UNKNOWN due to a bug in the UDP port mapping. When this occurs, GSS still functions correctly and the UDP ports work. You can verify that GSS is operating correctly by attempting to log in to GSS once the service has been deployed.