+++ This bug was initially created as a clone of Bug #1810841 +++
Description of problem:
This is our official documentation for placing infra workloads on infra nodes:
Its instructions won't work in many cases, because they don't assume that the cluster's default scheduler scheduler/cluster can be set with anything else other than the default worker.
Assuming it's unset is unrealistic. This is the first thing a customer who wishes to avoid apps starting on infra nodes will set after they build their infra nodes.
Every infra component then needs to override this setting - by adding (openshift.io/node-selector: "") to its namespace.
Most infra components already have this automatically done by the operator (openshift-monitoring, openshift-ingress-opertor, openshift-image-registry ). Two do not - openshift-ingress and openshift-logging.
Can we have this done by the Operator itself, i.e, adding a blank override?
Or can this just be done by a documentation bug itself? By adding the following workaround.
For the ingress router section, please add a blank override (openshift.io/node-selector: "") to the openshift-ingress namespace to look like this:
$ oc get ns/openshift-ingress -o yaml
For the logging section, please add a blank override (openshift.io/node-selector: "") to the openshift-logging namespace to look like this:
$ oc get ns openshift-logging -o yaml
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Scheduling Any components other than app workloads to infra nodes.
2. The default instructions in the documentation does not work in all scenarios.
Pods to be scheduled as per the requirement.
Corresponding Operator should be able to handle the task of having a label at the namespacelevel
Please suggest if just a documentation change is enough or if operator level change is needed as well.
Moving this one for logging team and I left the other 1810841 for the networking team.
(In reply to Maciej Szulik from comment #1)
> Moving this one for logging team and I left the other 1810841 for the
> networking team.
Since cluster-logging-operator is a OLM operator, we already instruct users to create the openshift-logging namespace with the empty node-selector annotation. This is done per doc entry , .
@Maciej Szulik: Are you fine with this approach?
I will defer to logging team to confirm the approach.
Since we address this issue already with docs I will close it.