OpenShift Pipelines: how to manage the QoS of TaskRun pods
Environment
-
Red Hat OpenShift Container Platform 4.x.
-
OpenShift Pipelines 1.x.
Issue
-
How can OpenShift Pipelines TaskRun pods be configured in order to control their QoS?
-
What is the default QoS of OpenShift Pipelines TaskRun pods?
-
Is there any way to set the QoS of all the OpenShift Pipelines TaskRun pods in a cluster to "Guaranteed"?
Resolution
-
The default QoS of TaskRun pods is "BestEffort".
-
As explained on Reducing resource consumption of OpenShift Pipelines, it is possible to set the QoS to "Burstable" by setting limits and requests in LimitRanges and task steps.
- The previous link points to the latest version, but the details to configure this may change for older releases. Please, make sure to check the documentation related to the version of the cluster being used.
-
Once SRVKP-2434 is implemented, it will be possible to set the QoS of all the OpenShift Pipelines TaskRun pods to "Guaranteed".
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments