This documentation is for a release that is no longer maintained
See documentation for the latest supported version 3 or the latest supported version 4.Este contenido no está disponible en el idioma seleccionado.
Chapter 8. Moving the cluster logging resources with node selectors
You can use node selectors to deploy the Elasticsearch, Kibana, and Curator pods to different nodes.
8.1. Specifying a node for cluster logging components using node selectors Copiar enlaceEnlace copiado en el portapapeles!
Each component specification allows the component to target a specific node.
Prerequisites
- Cluster logging and Elasticsearch must be installed. These features are not installed by default.
Procedure
Add the desired label to your nodes:
oc label <resource> <name> <key>=<value>
$ oc label <resource> <name> <key>=<value>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow For example, to label a node:
oc label nodes ip-10-0-142-25.ec2.internal type=elasticsearch
$ oc label nodes ip-10-0-142-25.ec2.internal type=elasticsearch
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Edit the Cluster Logging Custom Resource in the
openshift-logging
project:Copy to Clipboard Copied! Toggle word wrap Toggle overflow