Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-3444

[4.13] Descheduler pod is OOM killed when using descheduler-operator profiles on big clusters

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • 4.10
    • kube-scheduler
    • None
    • Moderate
    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      When deploying the Kube Descheduler Operator on a OCP Cluster
is not possible to modify the resources(request/limits) of the deployed pods.

This is problematic in big environments as it eventually hits an OOM scenario where the pod is restarting.

      Version-Release number of selected component (if applicable):

      4.10

      How reproducible:

      Always

      Steps to Reproduce:

      1. Deploy operator
2. Try to modify the resource values of the pod/deployment
3. Operator defaults the values back.

      Actual results:

      Not possible to change resources in the pod

      Expected results:

      Pod running with different resource values.

      Additional info:

       

        1. Screen Shot 2022-11-10 at 12.23.46 PM (2).png
          Screen Shot 2022-11-10 at 12.23.46 PM (2).png
          234 kB

              jchaloup@redhat.com Jan Chaloupka
              rhn-support-mblach Miguel Blach
              Paige Patton Paige Patton
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: