Kubernetes Cluster Validation
After you have installed your Kubernetes cluster, you're ready to meet with Solace to validate that cluster's readiness for the deployment of PubSub+ Cloud. If the cluster doesn't validate, you may need to reinstall or re-configure your cluster.
Solace provides the following prior to installing PubSub+ Cloud:
- Either a GCP JSON key file or a Pull Image Secret YAML file to enable access to Solace's
gcr.io
. - Instructions to run the tool that includes the commands to run the validation tool.
- The manifest YAML file needed by the tool to validate your cluster.
During the meeting, Solace has you run a validation tool. The tooling requires a registry secret, which is either a GCP JSON key file or a Pull Image Secret YAML file to enable access the Solace's Container Registry (gcr.io), and a manifest YAML file.
Solace helps you to understand the results of the validation and to help provide recommendations to address areas that didn't pass validation in your Kubernetes cluster. For example, the validation checks:
- that the necessary service accounts are configured with required permissions to your Kubernetes cluster
- the required resources are configured (such as CPUs, disk size, etc.)
- worker nodes are configured properly
- the connectivity of your Kubernetes cluster
- the prerequisites are fulfilled
- Kubernetes-specific type requirements are fulfilled
You meet with Solace to run the validation tool. Solace provides you with the details to get the proper YAML file to run on your cluster.
- Download the registry secret, which is either a GCP JSON key file or a Pull Image Secret YAML file to enable access the Solace Container Registry (gcr.io) where the images for the validation tooling is located.
- Download the validation tool manifest, which is a YAML file that is required by the cluster validation tool to validate your Kubernetes cluster.
-
You run the validation tool with assistance from Solace on your cluster.
- Review the results of running the validation tool with Solace. If necessary, modify your Kubernetes installation and rerun the tool.
If your Kubernetes cluster is validates, you're ready to install the Mission Control Agent. For more information, see Mission Control Agent Installation.