anchor.diff:  [[logging-node-selector]]
   *Node Selector*
   
  -Because Elasticsearch can use a lot of resources, all members of a
  -cluster should have low latency network connections to each other
  -and to any remote storage. Ensure this by directing the instances to
  -dedicated nodes, or a dedicated region within your cluster, using a
  -xref:../admin_guide/managing_projects.adoc#using-node-selectors[node
  -selector].
  -
  -To configure a node selector, specify the `*es-nodeselector*`
  -configuration option at deployment. This applies to all Elasticsearch
  -deployments; if you need to individualize the node selectors, you must
  -manually edit each deployment configuration after deployment.
  +Because Elasticsearch can use a lot of resources, all members of a cluster
  +should have low latency network connections to each other and to any remote
  +storage. Ensure this by directing the instances to dedicated nodes, or a
  +dedicated region within your cluster, using a
  +xref:../admin_guide/managing_projects.adoc#using-node-selectors[node selector].
  +
  +To configure a node selector, specify the `*es-nodeselector*` configuration
  +option at deployment. This applies to all Elasticsearch deployments; if you need
  +to individualize the node selectors, you must manually edit each deployment
  +configuration after deployment.
   
   [[aggregated-logging-persistent-storage]]
   *Persistent Elasticsearch Storage*
   
  -By default, the deployer creates an ephemeral deployment in which all of a pod's data is
  -lost upon restart. For production usage, specify a persistent storage volume for each
  -Elasticsearch deployment configuration. You may either create the necessary
  -xref:../architecture/additional_concepts/storage.adoc#persistent-volume-claims[PersistentVolumeClaims]
  -before deploying or have them created for you. The PVCs must be named based on
  -the `*es-pvc-prefix*` setting, which defaults to `logging-es-`; each PVC name will have
  -a sequence number added to it, so `logging-es-1`, `logging-es-2`, etc. If a PVC needed for
  -the deployment exists already, it will be used; if not, and `*es-pvc-size*` has
  -been specified, it will be created with a request for that size.
  +By default, the deployer creates an ephemeral deployment in which all of a pod's
  +data is lost upon restart. For production usage, specify a persistent storage
  +volume for each Elasticsearch deployment configuration. You can create
  +the necessary
  +xref:../architecture/additional_concepts/storage.adoc#persistent-volume-claims[persistent
  +volume claims] before deploying or have them created for you. The PVCs must be
  +named based on the `*es-pvc-prefix*` setting, which defaults to `logging-es-`;
  +each PVC name will have a sequence number added to it, so `logging-es-1`,
  +`logging-es-2`, and so on. If a PVC needed for the deployment exists already, it
  +is used; if not, and `*es-pvc-size*` has been specified, it is created with a
  +request for that size.
   
   [WARNING]
   ====
  -Using NFS storage as a volume or a PersistentVolume (or via NAS
  -such as Gluster) is not supported for Elasticsearch storage, as Lucene
  -relies on filesystem behavior that NFS does not supply. Data corruption
  -and other problems can occur. If NFS storage is a requirement, you can
  -allocate a large file on that storage to serve as a storage device and
  -treat it as a local mount on each host. For example:
  +Using NFS storage as a volume or a persistent volume (or via NAS such as
  +Gluster) is not supported for Elasticsearch storage, as Lucene relies on file
  +system behavior that NFS does not supply. Data corruption and other problems can
  +occur. If NFS storage is a requirement, you can allocate a large file on that
  +storage to serve as a storage device and treat it as a local mount on each host.
  +For example:
   
   ----
   $ truncate -s 1T /nfs/storage/elasticsearch-1
  
positive.code: |Description
  
  |*_kibana-hostname_*
  | The external host name for web clients to reach Kibana.
  
  |*_public-master-url_*
  |The external URL for the master. For OAuth purposes.
  
  |*_es-cluster-size_* (default: 1)
  | The number of instances of
  Elasticsearch to deploy. Redundancy requires at least three, and more can be
  used for scaling.
  
  
negative.code: must be at least 512M. Possible suffixes are G,g,M,m.
  
  |*_es-pvc-prefix_* (default: *logging-es-*)
  |Prefix for the names of persistent volume claims to be used as storage for
  Elasticsearch instances; a number will be appended per instance (for example,
  *logging-es-1*). If they do not already exist, they will be created with size
  *_es-pvc-size_*.
  
  |*_es-pvc-size_*
  |Size of the persistent volume claim to create per ElasticSearch instance, 100G,
  for example. If omitted, no PVCs are created and ephemeral volumes are used instead.
  
  |*_es-pvc-dynamic_*
  |Set to `*true*` to have created persistent volume claims annotated so that their
  backing storage can be dynamically provisioned (if that is available for your
  cluster).
  
  |*_storage-group_*
  |Number of a supplemental group ID for access to Elasticsearch storage volumes;
  backing volumes should allow access by this group ID (defaults to 65534).
  
  a|*_fluentd-nodeselector_* (default: *logging-infra-fluentd=true*)
  | A node selector that specifies which nodes are eligible targets
  for deploying Fluentd instances.
  All nodes where Fluentd should run (typically, all) must have this label
  