You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deployment/README.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -144,8 +144,11 @@ are available:
144
144
*`ES_INSTANCE_RAM`: Amount of RAM to reserve per ElasticSearch instance (e.g. 1024M, 2G). Defaults to 8GB; must be at least 512M (Ref.: [ElasticSearch documentation](https://www.elastic.co/guide/en/elasticsearch/guide/current/hardware.html#_memory).
145
145
*`ES_CLUSTER_SIZE` (required): How many instances of ElasticSearch to deploy. At least 3 are needed for redundancy, and more can be used for scaling.
146
146
*`FLUENTD_NODESELECTOR`: The nodeSelector to use for the Fluentd DaemonSet. Defaults to "logging-infra-fluentd=true".
147
+
*`ES_NODESELECTOR`: Specify the nodeSelector that Elasticsearch should be use (label=value)
148
+
*`KIBANA_NODESELECTOR`: Specify the nodeSelector that Kibana should be use (label=value)
149
+
*`CURATOR_NODESELECTOR`: Specify the nodeSelector that Curator should be use (label=value)
147
150
*`ENABLE_OPS_CLUSTER`: If "true", configure a second ES cluster and Kibana for ops logs. (See [below](#ops-cluster) for details.)
148
-
*`KIBANA_OPS_HOSTNAME`, `ES_OPS_INSTANCE_RAM`, `ES_OPS_CLUSTER_SIZE`: Parallel parameters for the ops log cluster.
151
+
*`KIBANA_OPS_HOSTNAME`, `ES_OPS_INSTANCE_RAM`, `ES_OPS_CLUSTER_SIZE`, `ES_OPS_NODESELECTOR`, `KIBANA_OPS_NODESELECTOR`, `CURATOR_OPS_NODESELECTOR`: Parallel parameters for the ops log cluster.
149
152
150
153
You run the deployer by instantiating a template. Here is an example with some parameters:
151
154
@@ -256,6 +259,10 @@ to each other. You will likely want to direct the instances to dedicated
256
259
nodes, or a dedicated region in your cluster. You can do this by supplying
257
260
a node selector in each deployment.
258
261
262
+
The deployer has options to specify a nodeSelector label for Elasticsearch, Kibana
263
+
and curator. If you have already deployed the EFK stack or would like to change
264
+
your current nodeSelector labels, see below.
265
+
259
266
There is no helpful command for adding a node selector. You will need to
260
267
`oc edit` each DeploymentConfig and add the `nodeSelector` element to specify
261
268
the label corresponding to your desired nodes, e.g.:
0 commit comments