Validating your starter deployment
Instead of manually checking all the URLs and certificates that are created by your deployment, you can run a script to validate these objects automatically in a few minutes.
Before you begin
Make sure that your client machine can connect to the cluster you want to use, and has the necessary tools. Install the appropriate tools from the following list.
- jq (a JSON processor open source tool)
-
- On macOS:
- How to install jq.
brew install jq
- Verify the installation.
jq –version jq --help
- How to install jq.
- On CentOS/RHEL:
- Install the EPEL Repository.
sudo yum install epel-release
- Update the packages.
sudo yum update
- Install jq.
sudo yum install jq
- Verify the installation.
jq --version jq --help
- Install the EPEL Repository.
- On macOS:
About this task
The post-installation script (cp4a-post-install.sh
) is found in the
cert-kubernetes repository. The script helps you to assess the readiness of
your CP4BA deployment, and to retrieve and validate connection information to all its services. For
more information about downloading cert-kubernetes, see Preparing for a starter deployment.
The cert-kubernetes/scripts/cp4a-post-install.sh script has four modes for a starter deployment type:
- precheck
- The
precheck
mode gets some basic information about the cluster, the console, and the client. - starterStatus
- The
starterStatus
mode gets the status of all the components from the custom resource (Ready
|Not Ready
|Not Installed
). - starterConsole
- The
starterConsole
mode gets the console connection information from the URLs and credentials. - starterProbe
- The
starterProbe
mode checks the readiness and health of the deployment endpoints.
The script can be run with the following options:
./cp4a-post-install.sh --help
--precheck This mode gives information about the cluster and the client.
--starterStatus This mode gives the status of the services of the CP4BA deployment.
--starterConsole This mode gives the service URLs of the consoles in the CP4BA deployment.
--starterProbe This mode checks the readiness of the deployment endpoints.
When you run the script in the starterStatus
, starterConsole
,
or starterProbe
mode, the commands display information about the Cloud Pak for Business Automation version and interim
fix number of the installed CP4BA deployment. The output also includes the list of CP4BA
capabilities that are installed.
If no CP4BA starter deployments are found on the cluster, then information about the cluster is displayed along with the following message:
No resources found for CP4BA Starter deployment types.
If no CP4BA starter deployments are found in the namespace in which you run the script, then information about the cluster is displayed along with the following message:
No CP4BA Starter deployment found in namespace NAMESPACE.