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

Ability to schedule Vertical pod autoscaler pods on Infra/worker nodes

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request

      Ability to schedule Vertical pod autoscaler pods on Infra nodes

      Currently, all pods run on master and Operator reverts if changes made in nodeselector in pod-deployments

      $ oc get pods -owide
      NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
      vertical-pod-autoscaler-operator-55c7bfd675-8qj95 1/1 Running 0 26m 10.129.0.51 master-0.lab.upshift.rdu2.redhat.com <none> <none>
      vpa-admission-plugin-default-6d6cc9d79c-r64jc 1/1 Running 0 25m 10.129.0.54 master-0.lab.upshift.rdu2.redhat.com <none> <none>
      vpa-recommender-default-c94695bfb-8kf82 1/1 Running 0 25m 10.129.0.53 master-0.lab.upshift.rdu2.redhat.com <none> <none>
      vpa-updater-default-c578f4c5d-jvlqt 1/1 Running 0 25m 10.129.0.52 master-0.lab.upshift.rdu2.redhat.com <none> <none>

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

      Customers want to run those pods on worker nodes or infra nodes so if it gets heavy we they enough resources

      ====
      KCS :https://access.redhat.com/solutions/7000413

            gausingh@redhat.com Gaurav Singh
            rhn-support-anisal Apurva Nisal
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: