anchor.diff:  logging infrastructure deploys.
   ====
   +
  +[NOTE]
  +====
  +Restricting the project will also restrict where Fluentd can be deployed.
  +It is instead recommended to specify node selectors on your Kibana and
  +Elasticsearch Deployment Configs once created.
  +
  +See link:#logging-node-selector[Node Selector] for examples on how to do this.
  +====
  ++
   Ensure that you switch to your new project before moving on to the next step. In
   this example, the project name is called `logging`:
   +
  
positive.code: ----
  ====
  
  === Fluentd
  
  Once Elasticsearch is running, scale Fluentd to every node to feed logs into
  
negative.code: You can use any volume type, such as
  link:../install_config/persistent_storage/persistent_storage_nfs.html[NFS].
  
  [[logging-node-selector]]
  *Node Selector*
  
  Because Elasticsearch can use a lot of resources, all members of a cluster should
  