Uploaded image for project: 'Docs for Red Hat Developers'
  1. Docs for Red Hat Developers
  2. RHDEVDOCS-4010

Incorrect description about moving the OpenShift Logging Operator pod to different nodes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Normal Normal
    • None
    • OpenShift 4.7 Async
    • Logging
    • ---
    • ---

      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:

              Unassigned Unassigned
              cbremble@redhat.com Claire Bremble
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: