Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1696444

Summary: [OCP4 Beta] NodeSelector missing for openshift-console, openshift-marketplace and openshift-monitoring
Product: OpenShift Container Platform Reporter: Stuart Auchterlonie <sauchter>
Component: NodeAssignee: Seth Jennings <sjenning>
Status: CLOSED DUPLICATE QA Contact: Jianwei Hou <jhou>
Severity: medium Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: aos-bugs, decarr, florin-alexandru.peter, gblomqui, jokerman, mmccomas
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-05 13:52:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stuart Auchterlonie 2019-04-04 20:45:34 UTC
Description of problem:


The operators that are responsible for the pods in the namespaces 
- openshift-console
- openshift-marketplace
- openshift-monitoring

have no option to configure the workload via an NodeSelector.

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

OCP4 HTB 3

How reproducible:

100%

Steps to Reproduce:
1. Deploy cluster
2. There is no NodeSelector available to configure the workload as desired
3.

Actual results:

NAMESPACE                                               NAME                                                              READY   STATUS      RESTARTS   AGE    IP             NODE                                      NOMINATED NODE
openshift-console                                       console-b9c5857bc-5l4vs                                           1/1     Running     2          99m    192.168.0.36   ocp4-nmz4m-master-1                       <none>
openshift-console                                       console-b9c5857bc-rgzpl                                           1/1     Running     2          99m    192.168.4.28   ocp4-nmz4m-master-0                       <none>
openshift-console                                       downloads-6d44bf7f79-9gtb6                                        1/1     Running     0          69m    192.168.20.4   ocp4-nmz4m-infra-s2large4-eude03-nxbfd    <none>
openshift-console                                       downloads-6d44bf7f79-scpk7                                        1/1     Running     0          99m    192.168.2.24   ocp4-nmz4m-master-2                       <none>


openshift-image-registry                                cluster-image-registry-operator-7c86588796-r5nl2                  1/1     Running     0          36m    192.168.0.60   ocp4-nmz4m-master-1                       <none>
openshift-image-registry                                image-registry-6f4c467764-vpk5j                                   1/1     Running     0          69m    192.168.10.4   ocp4-nmz4m-worker-s2large4-eude01-vgxwd   <none>


openshift-marketplace                                   certified-operators-6c77b455f6-msf6t                              1/1     Running     0          36m    192.168.14.6   ocp4-nmz4m-worker-s2large4-eude03-rwmgn   <none>
openshift-marketplace                                   community-operators-6d8cc6bf9b-66nb4                              1/1     Running     0          36m    192.168.20.6   ocp4-nmz4m-infra-s2large4-eude03-nxbfd    <none>
openshift-marketplace                                   marketplace-operator-6ffff946cc-tgt6b                             1/1     Running     0          36m    192.168.2.54   ocp4-nmz4m-master-2                       <none>
openshift-marketplace                                   redhat-operators-7d9f65c978-j6b88                                 1/1     Running     0          36m    192.168.20.7   ocp4-nmz4m-infra-s2large4-eude03-nxbfd    <none>


openshift-monitoring                                    alertmanager-main-0                                               3/3     Running     0          75m    192.168.14.4   ocp4-nmz4m-worker-s2large4-eude03-rwmgn   <none>
openshift-monitoring                                    alertmanager-main-1                                               3/3     Running     0          69m    192.168.10.6   ocp4-nmz4m-worker-s2large4-eude01-vgxwd   <none>
openshift-monitoring                                    alertmanager-main-2                                               3/3     Running     0          74m    192.168.12.4   ocp4-nmz4m-worker-s2large4-eude02-dzhp2   <none>
openshift-monitoring                                    cluster-monitoring-operator-588ccdfd49-2q8cf                      1/1     Running     0          36m    192.168.2.51   ocp4-nmz4m-master-2                       <none>
openshift-monitoring                                    grafana-9b484b898-drjjq                                           2/2     Running     0          69m    192.168.16.5   ocp4-nmz4m-infra-s2large4-eude01-8qqt9    <none>
openshift-monitoring                                    kube-state-metrics-5988dbb57b-bcqz2                               3/3     Running     0          69m    192.168.18.5   ocp4-nmz4m-infra-s2large4-eude02-79mgl    <none>
openshift-monitoring                                    node-exporter-67d28                                               2/2     Running     0          89m    10.0.0.161     ocp4-nmz4m-worker-s2large4-eude03-rwmgn   <none>
openshift-monitoring                                    node-exporter-7jxxp                                               2/2     Running     0          99m    10.0.0.9       ocp4-nmz4m-master-0                       <none>
openshift-monitoring                                    node-exporter-9l47r                                               2/2     Running     0          99m    10.0.0.11      ocp4-nmz4m-master-2                       <none>
openshift-monitoring                                    node-exporter-jhdf9                                               2/2     Running     0          99m    10.0.0.10      ocp4-nmz4m-master-1                       <none>
openshift-monitoring                                    node-exporter-mp4m5                                               2/2     Running     0          86m    10.0.2.46      ocp4-nmz4m-infra-s2large4-eude02-79mgl    <none>
openshift-monitoring                                    node-exporter-ps6jr                                               2/2     Running     0          85m    10.0.3.45      ocp4-nmz4m-infra-s2large4-eude03-nxbfd    <none>
openshift-monitoring                                    node-exporter-pwnxc                                               2/2     Running     0          88m    10.0.2.144     ocp4-nmz4m-infra-s2large4-eude01-8qqt9    <none>
openshift-monitoring                                    node-exporter-vkld2                                               2/2     Running     0          90m    10.0.2.231     ocp4-nmz4m-worker-s2large4-eude02-dzhp2   <none>
openshift-monitoring                                    node-exporter-w6cv9                                               2/2     Running     0          91m    10.0.1.255     ocp4-nmz4m-worker-s2large4-eude01-vgxwd   <none>
openshift-monitoring                                    prometheus-adapter-699cc99fcd-gdbr8                               1/1     Running     0          69m    192.168.12.5   ocp4-nmz4m-worker-s2large4-eude02-dzhp2   <none>
openshift-monitoring                                    prometheus-adapter-699cc99fcd-nl6qk                               1/1     Running     0          75m    192.168.14.5   ocp4-nmz4m-worker-s2large4-eude03-rwmgn   <none>
openshift-monitoring                                    prometheus-k8s-0                                                  6/6     Running     1          55m    192.168.16.6   ocp4-nmz4m-infra-s2large4-eude01-8qqt9    <none>
openshift-monitoring                                    prometheus-k8s-1                                                  6/6     Running     1          55m    192.168.10.7   ocp4-nmz4m-worker-s2large4-eude01-vgxwd   <none>
openshift-monitoring                                    prometheus-operator-7cc6c6d958-clqth                              1/1     Running     0          69m    192.168.20.5   ocp4-nmz4m-infra-s2large4-eude03-nxbfd    <none>
openshift-monitoring                                    telemeter-client-7ccbf5bd8d-cwxj7                                 3/3     Running     0          69m    192.168.12.6   ocp4-nmz4m-worker-s2large4-eude02-dzhp2   <none>

Expected results:

the idea is to move the console pods or the monitoring pods as a day 2 operation task to the infra nodes.


Additional info:

Comment 2 Greg Blomquist 2019-04-05 13:22:23 UTC
OCP 4.x is specifically designed to not allow node selection for those components.  Moving this out to 4.2 to give time to discuss whether we want to change OCP 4.x to allow for nodeSelectors on these workloads.  It's possible we'll close this as wontfix if we determine this isn't the desired product direction.

Comment 3 Derek Carr 2019-04-05 13:43:53 UTC
The prior comment is not correct - the console and the monitoring components can be moved to other nodes.

I am duplicating these bugs to each component so we can close with proper documentation.

Comment 4 Derek Carr 2019-04-05 13:52:46 UTC

*** This bug has been marked as a duplicate of bug 1696724 ***

Comment 5 Derek Carr 2019-04-05 13:58:50 UTC
Documentation tracker bugs for the following have been opened.

Console:
https://bugzilla.redhat.com/show_bug.cgi?id=1696724

Monitoring:
https://bugzilla.redhat.com/show_bug.cgi?id=1696725

Marketplace:
https://bugzilla.redhat.com/show_bug.cgi?id=1696726