Configuration templates

Use the generic CommonService custom resource template to configure the services before you install them in your cluster.

For the sizing updates, see Hardware requirements and recommendations for foundational services.

When multiple IBM Cloud Pak®s are installed in your cluster, each IBM Cloud Pak might configure the same service with different configuration parameters. For example, IBM Cloud Pak A might specify the hardware profile as size: small and IBM Cloud Pak B might specify the hardware profile as size: large. IBM Cloud Pak foundational services resolves such differences by applying the following rules:

For the hardware profile, the largest profile is deployed in the cluster.
For the service-specific resource limits and requests, the largest resource limit and request is set.
For some configuration parameters, such as storage class and replicas, the first configuration that was set is always retained. If the parameter was already set by an IBM Cloud Pak, even if you update the value in the CommonService custom resource, the value that was first set is retained. For more information, see Storage class.

For the most recent updates to the hardware specifications, see ibm-common-service-operator Opens in a new tab .

Generic CommonService custom resource template

The generic template is for providing the service-specific configurations in the CommonService custom resource. For the complete list of available configurations, see Configuring IBM Cloud Pak foundational services by using the CommonService custom resource.

apiVersion: operator.ibm.com/v3
kind: CommonService
metadata:
  name: common-service
  namespace: <your-foundational-services-namespace>
spec:
  services:
  - name: <common-service-operator-name>
    spec:
      <container-name>:
        replicas: <number-of-replicas (if supported)>
        resources:
          limits:
            cpu: <cpu-limit>
            memory: <memory-limit>
            ephemeral-storage: <ephemeral-storage-limit>
          requests:
            cpu: <cpu-request>
            memory: <memory-request>
            ephemeral-storage: <ephemeral-storage-request>

The following example is a CPU limit configuration for cert-manager certManagerCAInjector.

apiVersion: operator.ibm.com/v3
kind: CommonService
metadata:
  name: common-service
  namespace: <your-foundational-services-namespace>
spec:
  services:
  - name: ibm-cert-manager-operator
    spec:
      certManager:
        certManagerCAInjector:
          resources:
            limits:
              cpu: 150m

For more information about configuring services and operators, see Configuring IBM Cloud Pak foundational services by using the CommonService custom resource.

To apply your configuration changes, create a yaml file and run the following command:

oc apply -f <yaml-name-name>.yaml