Customizing limits and requests of License Service resources

You can change the default resource limits and requests to custom values for the resources that are managed by License Service.

This feature is available from License Service version 4.2.5.

You can change the following resource limits and requests:

• cpu
• memory
• hugepages-<size>, where <size> is size of the hugepages that are configured on the cluster nodes, for example, 2Mi. For more information, see Manage HugePages in Kubernetes documentation.

Note: The best practice is to set both custom limits and requests for resources to avoid conflicts with the default values that are set by the operator.

Complete the following steps:

1. Open the License Service custom resource (CR).

   • From the OpenShift console:

     1. Log in to your OpenShift console.
     2. Go to Operators > Installed Operators.
     3. From the Project drop-down list, select All Projects
     4. Select IBM Licensing.
     5. Select the IBM License Service tab. The instance of License Service custom resource is listed.
     6. From the overflow action menu, select Edit IBMLicensing.

   • From the command line:

     Run the following command:

        kubectl edit IBMLicensing instance -n ibm-licensing
     

     Note: The recommended namespace for License Service installation is ibm-licensing. The command contains this default namespace. However, you can install License Service in any other custom namespace. If you installed License Service in a custom namespace, replace ibm-licensing with the name of the custom namespace.

2. Edit limits and requests for your License Service resources. Provide custom resource limits and requests in the CR by changing values for one or more resources. For example:

    spec:
      resources:
        limits:
          cpu: 500m
          memory: 2Gi
          hugepages-2Mi: 100Mi
        requests:
          cpu: 200m
          memory: 1Gi
          hugepages-2Mi: 100Mi
   

3. Save the CR to apply the changes.

For more information about types of resources, see Resource Management for Pods and Containers in Kubernetes documentation.