IBM C1000-150 - IBM Cloud Pak for Business Automation v21.0.3 Administration

The Cloud Pak Foundation services monitoring stack includes Kibana, which is an open-source data visualization and exploration tool. It allows you to search, view, and interact with data stored in Elasticsearch indices. Kibana provides a web interface that enables you to create and share dynamic dashboards, visualizations, and search templates.

It's important to note that other tools such as Elasticsearch, Alertmanager, and Logstash are also part of the Cloud Pak Foundation services monitoring stack, but they have different functions.

If security pods are not scheduled, then a Cloud Pak for Business Automation Administrator should check the Resource Registry as it may not be correctly configured. The Resource Registry is the central repository for all resources used by the pods and is used to define the resources used by the pods.

References: [1] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/cpd/administer/res_registry.html  [2] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/cpd/administer/overview.html

If it is desired to use a root CA signer certificate that is signed by a recognized certificate authority, the rootcacertificate should be supplied as part of the custom resource prior to deployment. This is necessary in order for the root CA signer certificate to be validated.

References: [1] https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-certificates/#running-an-https-server  [2] https://kubernetes.io/docs/concepts/cluster-administration/certificates/

After scaling a Process Mining deployment, the replica set values for COMPLETED and DESIRED are updated.

References: [1] https://docs.camunda.org/manual/7.11/process-mining/technical-setup/  [2] https://docs.camunda.org/manual/7.11/process-mining/configuration/

IBM Cloud Pak foundational services monitoring requires Role-based access control (RBAC) to monitor APIs and data. This ensures that only authorized users have access to the data and APIs that are being monitored. It also ensures that data is only being accessed by users with the appropriate permissions. Kibana is used as the data source for the Cloud Pak foundational services monitoring. Adopter customization is only necessary to query and visualize application metrics. Red Hat OpenShift Container Platform monitoring is not required for Cloud Pak foundational services monitoring.

References: [1] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/monitoring/overview.html  [2] https://www.ibm.com/support/knowledgecenter/SSFTN5_2.2.2/monitoring/rbac.html

The rpa-owner permission must be granted in order for the option to appear in the Platform UI navigation menu. If you would like to grant the permission, please follow these steps: 1) Log into the Robotic Process Automation (RPA) server 2) Navigate to the Settings tab 3) Select the Security tab 4) Select the Roles & Permissions tab 5) Select the rpa-owner permission 6) Click Save.

Secrets on Kubernetes master (API server) are not encrypted by default at rest, extra steps are needed to encrypt them. Kubernetes does not automatically encrypt secrets at rest, it is the responsibility of the user to ensure that the secrets are encrypted. There are several ways to encrypt secrets at rest, such as using Kubernetes native encryption, third-party encryption tools or using a cloud provider's encryption services.

Migrating data from a Cloud Pak for Business Automation version that does not support an upgrade requires an Administrator to uninstall the current deployment and follow the migration instructions for each component, pointing them to the existing persistent stores

When migrating data from Cloud Pak for Business Automation versions that do not support an upgrade, an Administrator must uninstall the current deployment and follow the migration instructions for each component to point to the existing persistent stores. This process involves migrating data from the existing databases and persistent volumes to the new deployment. This process may also require creating new configurations and customizing the new deployment to match the previous one.

The command "oc get pods -n NAMESPACE" is used to verify that all the pods are running after Operators are deployed. This command allows you to view the status of all pods in a specific namespace, which is useful for troubleshooting issues and ensuring that all pods are running correctly. The command will show the name, status, and other information about each pod in the specified namespace.

It's important to note that the other commands such as oc debug pods, oc describe pods, and oc status pods can also be used to troubleshoot issues but oc get pods is the command that is used to verify that all the pods are running after Operators are deployed.