Customizing limits and requests of License Service Reporter resources

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

This feature is available from License Service Reporter version 4.2.3.

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.

Custom resource values are supported for all containers inside the License Service Reporter pod, such as, receiverContainer, databaseContainer, reporterUIContainer and authContainer.

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.

To customize limits and requests of License Service Reporter resources, complete the following steps:

1. Open the License Service Reporter 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 License Service Reporter.
     5. Select the IBM License Service Reporter tab. The instance of License Service Reporter custom resource is listed.
     6. From the overflow action menu, select Edit IBMLicenseServiceReporter.

   • From the command line:

     Run the following command:

     kubectl edit IBMLicenseServiceReporter instance -n <License Service Reporter namespace>
     

   where <License Service Reporter namespace> is the name of the namespace where License Service Reporter is installed.

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

    spec:
      receiverContainer:
        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.