Details
-
Feature Request
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
0
-
0%
Description
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
Attachments
Issue Links
- is related to
-
-
- In Progress
-