Recommended: Validating your production 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.
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 a client to connect to the cluster.
After you downloaded the CASE package and extracted the cert-kubernetes
archive, change directory to the /scripts folder under
ibm-cp-automation/inventory/cp4aOperatorSdk/files/deploy/crs/cert-kubernetes.
The /scripts
folder is the root folder ($ROOT_FOLDER
) of the
post-installation script.
The cp4a-post-install.sh
script has three modes for a production deployment
type:
- precheck
- The
precheck
mode gets some basic information about the cluster, the console, and the client. - status
- The
status
mode gets the status of all the components from the custom resource (Ready
|Not Ready
|Not Installed
). - console
- The
console
mode gets the console connection information from the URLs and credentials.
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.
--status This mode gives the status of the services of the CP4BA deployment.
--console This mode gives the service URLs of the consoles in the CP4BA deployment.
When you run the script in the status
or console
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 production deployments are found on the cluster, then information about the cluster is displayed along with the following message:
No resources found for CP4BA Production deployment types.
If no CP4BA production 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 Production deployment found in namespace NAMESPACE.
Procedure
What to do next
Some capabilities need you to follow post-deployment steps. For more information, see Completing post-installation tasks.