Adjust resource quotas

With resource quotas, cluster administrators can restrict resource consumption and creation on a namespace basis. There will always be concerns that one Pod or Container could monopolize all available resources. To avoid that, within a namespace, a Pod or Container can consume as much CPU and memory as defined by the namespace’s/project’s resource quota.

To discover the resource quota established for your namespace/project you can run the following command:

At namespace/project level a LimitRange policy is employed to constrain resource allocations (to Pods or Containers). You can find out the LimitRange established for a namespace by running oc get limitrange and ask for its description via:

The output should be something similar to:

The above LimitRange has enforced the default request/limit for compute resources in the namespace and automatically injects them to Containers at runtime.

By using a tool called hey, you can run a load test on your server and see how your system performs under different circumstances.

Let’s run a hey command against the route exposed by previous deployment:

In the Developer Sandbox click on Observe and select the Metric tab. You can select CPU Usage or Memory Usage query to check the resources consumed by each of your pods:

Based on that you can adjust your container resources in application.properties:

The resources in target/kubernetes folder will be reworked at compile time and contain these new definitions.

You can now deploy the changes by using the command: