anchor.diff:  apiVersion: "logging.openshift.io/v1alpha1"
   kind: "ClusterLogging"
   metadata:
  -  name: "instance"  <1>
  +  name: "instance"
     namespace: "openshift-logging"
   spec:
  -  managementState: "Managed" <2>
  +  managementState: "Managed"
     logStore:
  -    type: "elasticsearch" <3>
  +    type: "elasticsearch"
       elasticsearch:
         nodeCount: 3
         storage: {}
         redundancyPolicy: "SingleRedundancy"
     visualization:
  -    type: "kibana" <4>
  +    type: "kibana"
       kibana:
         replicas: 1
     curation:
  -    type: "curator" <5>
  +    type: "curator"
       curator:
         schedule: "30 3 * * *"
  -  collection:  <6>
  +  collection:
       logs:
         type: "fluentd"
         fluentd: {}
   ----
  -<1> The name of the Cluster Logging Custom Resource.
  -<2> The cluster logging management state. In most cases, if you change the default cluster logging defaults, you will need to set this to `Unmanaged`. 
  -However, an unmanaged deployment does not receive updates until the cluster logging is placed back into a managed state.
  -<3> Settings for configuring Elasticsearch. Using the CR, you can configure shard replication policy and persistent storage.
  -<4> Settings for configuring Kibana. Using the CR, you can scale Kibana for redundancy and configure the CPU and memory for your Kibana nodes.
  -<5> Settings for configuring Curator. Using the CR, you can set the Curator schedule.
  -<6> Settings for configuring Fluentd. Using the CR, you can configure Fluentd CPU and memory limits.
  -+
  -See the links in the Table of Contents for more information on configuring these and other cluster logging components.
  -+
  -[NOTE]
  -====
  -The default cluster logging configuration should support a wide array of environments. Review the topics on tuning and configuring the cluster logging
  -components for information on modifications you can make to your cluster logging cluster.
  -==== 
   
   .. Click *Create*. This creates the Cluster Logging Custom Resource, which you
   can edit to make changes to your cluster logging cluster.
  
positive.code: .. Ensure that *Cluster Logging* and *Elasticsearch Operator* are listed on
  the *InstallSucceeded* tab with a *Status* of *InstallSucceeded*. Change the project to *all projects* if necessary.
  +
  If either operator does not appear as installed, to troubleshoot further:
  
  * On the *Copied* tab of the *Installed Operators* page, if an operator show a *Status* of
  
negative.code: * Switch to the *Workloads* → *Pods* page and check the logs in any Pods in the
  `openshift-logging` and `openshift-operators` projects that are reporting issues.
  
  . Create a cluster logging instance:
  
  .. Switch to the the *Administration* -> *CRD* page.
  
  