Changing CRI-O container settings (Upgrading from Version 3.5 to Version 4.6)

To ensure that some services can run correctly, you might need to change the pids_limit setting for the CRI-O container runtime on the OpenShift® Container Platform.
Upgrade phase
You are not here. Setting up a client workstation
You are not here. Collecting required information
You are here icon. Preparing your cluster
You are not here. Upgrading the Cloud Pak for Data platform and services
Who needs to complete this task?
A cluster administrator must complete this task.
When do you need to complete this task?
When you plan to install certain services, you must change node settings to configure your cluster so those services run properly.

Before you begin

Best practice: You can run the commands in this task exactly as written if you set up environment variables. For instructions, see Setting up installation environment variables.

Ensure that you source the environment variables before you run the commands in this task.

About this task

Whether you need to change pids_limit value and how you change it depend on your environment. If you plan to install one or more of the following services, you might need to adjust the pids_limit:
  • Cognos® Analytics
  • Db2®
  • Db2 Big SQL
  • Db2 Warehouse
  • Watson™ Discovery
  • Watson Knowledge Catalog
  • Watson Query
  • Watson Studio
  • Watson Machine Learning Accelerator

Procedure

Complete the appropriate task for your environment, as specified in the following table:

Deployment environment Managed Self-managed
On-premises If you install Cloud Pak for Data on IBM® Cloud Satellite, the CRI-O container settings are automatically applied to your cluster as part of the installation. You do not need to change the CRI-O settings.
OpenShift Version 4.8 and Version 4.10
See Setting the pids_limit by using the cpd-cli manage apply-crio command.
OpenShift Version 4.12
See #crio-settings__d496e700.
IBM Cloud If you install Cloud Pak for Data on IBM Cloud, the CRI-O container settings are automatically applied to your cluster as part of the installation. You do not need to change the CRI-O settings. If you install Cloud Pak for Data on IBM Cloud, the CRI-O container settings are automatically applied to your cluster as part of the installation. You do not need to change the CRI-O settings.
AWS
OpenShift Version 4.8 and Version 4.10
See Setting the pids_limit by using the cpd-cli manage apply-crio command.
OpenShift Version 4.12
See #crio-settings__d496e700.
Important: To change this setting on Red Hat® OpenShift Service on AWS (ROSA) you might need a Support Exception from Red Hat. For more information, see https://access.redhat.com/solutions/6986931 on the Red Hat Customer Portal.
OpenShift Version 4.8 and Version 4.10
See Setting the pids_limit by using the cpd-cli manage apply-crio command.
OpenShift Version 4.12
See #crio-settings__d496e700.
Microsoft Azure
OpenShift Version 4.8 and Version 4.10
See #crio-settings__d496e760.
OpenShift Version 4.12
See #crio-settings__d496e700.
Important: To change this setting on Azure Red Hat OpenShift (ARO) you must have a Support Exception from Red Hat. For more information, see https://access.redhat.com/solutions/6986931 on the Red Hat Customer Portal.
OpenShift Version 4.8 and Version 4.10
See #crio-settings__d496e760.
OpenShift Version 4.12
See #crio-settings__d496e700.
Google Cloud Not applicable
OpenShift Version 4.8 and Version 4.10
See Setting the pids_limit by using the cpd-cli manage apply-crio command.
OpenShift Version 4.12
See #crio-settings__d496e700.