Downloading the Registry Credentials for the Solace Container Registry

Before beginning, ensure your cluster has access to the Solace Container Registry as outlined in the Connectivity Model for Kubernetes Deployments.

Solace provides the registry secret (authorization token) to access the Solace Container Registry (gcr.io) where the container images are stored. This is provided as a JSON or YAML file that allows you to pull images (the available file type is based on your Kubernetes configuration) from the gcr.io.

You require these credentials to install the Kubernetes cluster, which can download the <datacenter-id>-pull-secret.yaml or the <datacenter-id>-registry-credentials.json file.

If you organization doesn't allow you to download images from your VPC/VNet, you can set up an internal mirror site for the Solace Container Registry (gcr.io).

To download the registry secret ( <datacenter-id>-pull-secret.yaml or the <datacenter-id>-registry-credentials.json file), perform the following steps:

  1. Log in to the PubSub+ Cloud Console if you have not done so yet. The URL to access the Cloud Console differs based on your authentication scheme. For more information, see Logging into the PubSub+ Cloud Console.

  2. On the navigation bar, click User & Account and then select Account Details.
  3. On the Account Details page, select the Private Regions tab.
  4. Click on the ellipse icon () for a listed Datacenter.

  5. The menu that opens presents one of two options based on your Kubernetes configuration:

    • Download Image Pull Secret—Securely downloads a <datacenter-id>-pull-secret.yaml file containing a manifest for Kubernetes to your local storage drive via TLS.
    • Download Registry Credentials—Securely downloads a <datacenter-id>-registry-credentials.json registry credentials file for Kubernetes to your local storage drive via TLS.

    You can use the contents of either of these files as an authorization token to access the Solace Container Registry (gcr.io) where Solace's container images are stored. For more about deploying Mission Control Agent into your Kubernetes cluster, see Kubernetes Cluster Installation.

For more information, see Private Regions.