Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-3758

`cpu-quota.crio.io: disable` annotation by default for Guaranteed QoS pods

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Unresolved
    • Undefined
    • None
    • None
    • None
    • False
    • None
    • False
    • Not Selected
    • 0
    • 0% 0%

    Description

      1. Proposed title of this feature request

      `cpu-quota.crio.io: disable` annotation by default for Guaranteed QoS pods

      2. What is the nature and description of the request?

      According to the documentation https://docs.openshift.com/container-platform/4.12/scalability_and_performance/cnf-low-latency-tuning.html#managing-device-interrupt-processing-for-guaranteed-pod-isolated-cpus_cnf-master, there are some configurations that are optional and some that are not optional. For the `cpu-quota.crio.io: disable` that is mandatory it should be able to be added by default from the platform.

      3. Why does the customer need this? (List the business requirements here)

      DPDK pod that are installed using a generic deployment method not tailored to OCP (e.g. HELM) should be able to run in OCP out of the box.

      4. List any affected packages or components.
      CRIO/Tuned

      Attachments

        Activity

          People

            msivak@redhat.com Martin Sivak
            kkarampo@redhat.com Konstantinos Karampogias
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated: