Mission Control Agent Installation

If your Kubernetes deployment uses the NO_PROXY environment variable, addresses contained in the variable cannot contain metadata characters (for example, *). The Mission Control Agent does not support the use of metadata characters in IP addresses that should bypass the proxy. For example, use addresses such as .example.com, instead of *.example.com.

After you have validated your Kubernetes cluster, you're ready to meet with Solace to install the Mission Control Agent. As part of the installation of Mission Control Agent, service accounts are created in your Kubernetes cluster. For more information about the service accounts, see Service Accounts in Kubernetes.

The Mission Control if installed successfully allows to you to create event broker services.

Solace provides the following prior to installing PubSub+ Cloud:

  • Either a JSON key file or a Pull Image Secret YAML file to enable access to Solace's  Container Repository (gcr.io). This is the same secret you used to access the gcr.io to access the validation tool.
  • The location of the image repository, for example gcr.io/gcp-maas-prod.
  • The container image name and tag.

During the meeting, with Solace, the following occurs

  1. If you haven't done so yet, download the registry credentials.
  2. Solace creates the parameters file, which you download. For more information, see Downloading the Values File for Helm Chart.
  3. Solace provides you the URL of the Helm chart to run.
  4. You run the commands to install Mission Control Agent to your Kubernetes cluster. Solace is available to answer questions and during this time. For more information, see Installing the Mission Control Agent.

After the installation completes, you can create a test service to validate the installation. For more information, see Creating Event Broker Services.