Remove resource limits in OpenShift

[chrislaick]

After meeting with AppOps team on Jan 8th, they recommended we remove the resource limits in OpenShift for our Drupal projects, as recommended by the Platform Services team in an email dated Dec 10, 2024. Pay Transparency and Airflow projects and have resource limits removed without any adverse effects.

Dear OpenShift Project Teams,

We’re excited to share that as of this morning, December 10, 2024, we’ve made updates to the Quota section to enhance its flexibility and usability:

Removal of Resource Limits - The concept of limit has been removed. OpenShift now uses only request values configured by the OpenShift Provisioner.

What this means: Resource requests configured for a namespace are always guaranteed, while additional resources are only available when node capacity allows.

Why limits were removed: Setting CPU limits on Kubernetes can lead to inefficiencies and CPU throttling, even when additional resources are available. By relying on requests, we ensure that resources are reserved for critical workloads without unnecessary constraints, enabling optimal resource utilization and preventing CPU starvation.

Enhanced Numeric Input Options

To provide greater flexibility, the UI now features numeric inputs instead of dropdowns, enabling more precise resource allocation:

CPU: Adjustable from 0 to 64 cores in 0.5-core increments.

Memory: Adjustable from 0 to 128 GB in 1 GB increments.

Storage: Adjustable from 0 to 512 GB in 1 GB increments.

If you have any concerns or questions, please reach out to us via [email redacted].

Regards,
Platform Services Team

See example commit from Pay Transparency project. We can ignore the requests change:

bcgov/fin-pay-transparency@3320506