Ongoing maintenance (Day 2 operations)

Complete ongoing maintenance tasks as necessary to keep IBM Cloud Pak for Data running and to make adjustments to your environment.

Best practices for monitoring Cloud Pak for Data
It is critical to monitor the health of your IBM Cloud Pak for Data environment on a regular basis. By monitoring your Cloud Pak for Data deployments and the clusters where your deployments are running, you can ensure that the environment is performant and is scaled to support your business needs. In addition, routine monitoring can help prevent unexpected outages and instability.
Monitoring the platform
From the IBM Cloud Pak for Data web client, you can monitor the services that are running on the platform, understand how you are using cluster resources, and be aware of issues as they arise. You can also set quotas on the platform, individual services, and on projects to help mitigate unexpected spikes in resource use.
Creating announcements that are displayed in the web client
An IBM Cloud Pak for Data administrator can create announcements to let users know about upcoming maintenance or planned outages. The announcements are displayed below the toolbar until they expire.
Audit events
The following topics describe the audit events that are generated by various components of the platform.
Managing resources
After IBM Cloud Pak for Data is deployed on your Red Hat® OpenShift® cluster, cluster and project administrators might need to complete tasks to ensure that services can run smoothly on the cluster, and that the cluster has the appropriate resources.
Configuring node scoring for the scheduling service
You can adjust the node scoring configuration for the scheduling service if you want to have more control over where the IBM Cloud Pak for Data scheduling service schedules pods.
Customizing pod specifications with resource specification injection
The IBM Cloud Pak for Data resource specification injection (RSI) feature enables you to extend Kubernetes resources that are associated with IBM Cloud Pak for Data by applying patches directly to pods that are associated with Kubernetes deployments, StatefulSets, replicasets, replicacontrollers, jobs, and cronjobs.
Migrating data between instances of Cloud Pak for Data
You can migrate data between your IBM Cloud Pak for Data deployments. For example, you might want to export the data from a development environment and import it to a production environment.
Managing storage volumes
You can create and manage connections to storage volumes from IBM Cloud Pak for Data.
Managing secrets and vaults
Cloud Pak for Data includes an internal vault that you can use to store secrets. You can also connect to external vaults where you already store sensitive information as secrets.
Administering connectors
Some connectors require that an administrator upload one or more JDBC driver files. An administrator can also create a custom JDBC connector that can be used for multiple connections to a data source. Alternatively, users can use the drivers to create a single Generic JDBC connection.
Gathering diagnostic information
You can gather diagnostic information to be sent to IBM® Support when a problem arises.

Parent topic: Administering Cloud Pak for Data