Deployments in China

Deployments in China require additional considerations due to the business and technical differences when compared to other regions. Due to these differences, Solace only supports deployments in China to Customer-Controlled Regions. At this time, Solace does not support deployments to Public Regions and Dedicated Regions.

Solace supports deploying PubSub+ Cloud to the following Kubernetes providers in China:

Solace also supports on-premises Kubernetes deployments using various distributions, including OpenShift, Rancher (RKE1), Rancher (RKE2), and VMware Tanzu Kubernetes Grid (TKG). For more information, contact Solace.

Considerations for Deployments in China

You should be aware of the following considerations when deploying PubSub+ Cloud to a Customer-Controlled Region in China:

  • Your Customer-Controlled Region requires a custom domain name registered in China, for example *.mycompany.cn with certificates issued for that domain. The custom domain name means you access your event broker services using the provided custom domain name instead of *.messaging.solace.cloud. For more information, see Configuring Custom Domain Names for Event Broker Services.

  • Instead of the GCP registry, you must use the Azure China registry. The Azure China registry uses a different secret that's required when you later deploy the Mission Control Agent. For example, run the following command where the <username> and <password> is provided by Solace.

    • kubectl create secret docker-registry cn-reg-secret --namespace kube-system \ 
    --docker-server=solacecloud.azurecr.cn --docker-username=<username>  --docker-password=<password>

  • You can choose public, private, or hybrid connectivity for your Customer-Controlled Region deployments in China.

  • Solace recommends setting up your cluster with availability zones when available to increase the resilience of your high-availability event broker services.