Bug 1982491

Summary:	Incorrect description about moving the OpenShift Logging Operator pod to different nodes
Product:	OpenShift Container Platform	Reporter:	yhe
Component:	Documentation	Assignee:	landerso
Status:	CLOSED NOTABUG	QA Contact:	Anping Li <anli>
Severity:	medium	Docs Contact:	Preeti Chandrashekar <pchandra>
Priority:	unspecified
Version:	4.7	CC:	aos-bugs, cbremble
Target Milestone:	---
Target Release:	---
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:	2022-04-29 16:48:40 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 yhe 2021-07-15 02:52:16 UTC

Document URL: 
https://docs.openshift.com/container-platform/4.7/logging/config/cluster-logging-moving-nodes.html#infrastructure-moving-logging_cluster-logging-moving

Section Number and Name: 
Moving OpenShift Logging resources

--> You cannot move the Red Hat OpenShift Logging Operator pod from its installed location.

Describe the issue: 
OpenShift Logging Operator pod (and Elasticsearch Operator pod) can be moved to different nodes by adding the following annotation to the namespaces and recreate the pods:

apiVersion: v1
kind: Namespace
metadata:
  name: openshift-logging
  annotations:
    openshift.io/node-selector: node-role.kubernetes.io/infra=
  labels:
    openshift.io/cluster-monitoring: "true"

apiVersion: v1
kind: Namespace
metadata:
  name: openshift-operators-redhat 
  annotations:
    openshift.io/node-selector: node-role.kubernetes.io/infra=
  labels:
    openshift.io/cluster-monitoring: "true"

Suggestions for improvement: 
Modify the incorrect description and explain the method to move the OpenShift Logging Operator pod and Elasticsearch Operator pod.

Additional information: