-
Bug
-
Resolution: Done
-
Normal
-
None
-
5
-
False
-
-
True
-
-
-
OBSDOCS (Mar 25 - Apr 15) #251
-
Moderate
Description of problem: The documentation for scaling infrastructure nodes for migrating the openshift-logging stack are incorrect on the taints.
How reproducible:
Follow the documentation: https://docs.openshift.com/container-platform/4.14/machine_management/creating-infrastructure-machinesets.html Attempt to create the machine sets and migrate the logging subsystem
Actual results:
All elastic and kibana pods will be stuck in a pending state. Pod unschedulable0/29 nodes are available: 23 node(s) didn't match Pod's node affinity/selector, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }, 3 node(s) had volume node affinity conflict. preemption: 0/29 nodes are available: 29 Preemption is not helpful for scheduling..
Expected results:
Pods should be in a running state
Additional info:
To fix this issue the infrastructure machine set has to be created with the following taints: taints: - key: node-role.kubernetes.io/infra effect: NoSchedule - key: node-role.kubernetes.io/infra effect: NoExecute value: reserved This will resolved the pending issue and allow pods to populate to the nodes correctly.
- is related to
-
OBSDOCS-760 Improve documentation around taints, tolerations, and node selectors for logging
- Closed
- links to
(2 links to)