-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
4.18
-
None
-
Product / Portfolio Work
-
None
-
False
-
-
None
-
None
-
None
-
-
None
-
None
-
None
-
None
-
None
Proposed title of this feature request
Place the openshift-console download server pods in master nodes
What is the nature and description of the request?
In openshift-console namespace download server pods are part of of core components of OCP. Out-of-the box there are running on worker nodes whereas web console pods are running in master nodes.
Note also currently download server pods have already a toleration node-role.kubernetes.io/master but the node selector is missing to assign them the master nodes.
To be consistent with our OCP deployment and to reduce our internal component footprint on worker nodes (which consume subscriptions), we should relocate them in master nodes by adding a node selector in their deployment.
Why does the customer need this? (List the business requirements here)
Customer wants to avoid any OCP internal components workload to run on worker nodes which could consume unecessary subscriptions.
List any affected packages or components
Download server deployment descriptor