anchor.diff:  .. Verify that the log store is updated to 4.5 and the indices are `green`:
   +
   ----
  -oc exec -c elasticsearch <any_es_pod_in_the_cluster> -- indices 
  +oc exec -c elasticsearch <any_es_pod_in_the_cluster> -- indices
   ----
   +
   You should see the `app-0000x`, `infra-0000x`, `audit-0000x`, `.security` indices.
  
positive.code: 
  If you use Kibana, after the Elasticsearch Operator and Cluster Logging Operator are fully updated to 4.5, you must perform the following actions to complete the upgrade:
  
  * Recreate your Kibana index patterns. Because of changes in the security plug-in, the cluster logging upgrade does not automatically create index patterns. 
  
  ** Regular users must manually create index patterns to see logs for their projects. Because of the new Elasticsearch data model, all logs that were stored in an index prefixed with *project-* in {product-title} 4.4 are now in a set of indices prefixed with *app-*. Users should create a new index patterns named `app` and use the `@timestamp` time field to view their container logs. To view historical data gathered by cluster logging 4.4, users need to create index patterns using `project*` field.
  
  ** Admin users need to create index patterns using the *app*, *infra* and *audit* prefix with the `@timestamp` time field. The *infra-* indices were previously *.opertions-*. The *audit-* indices are the audit logs. To view historical data gathered by cluster logging 4.4, admin users need to create index patterns using the `.operation*` field to view system logs and create index patterns using the `project*` field to view project-level logs.
  
  * Recreate your Kibana Visualizations to use the new index patterns. 
  
negative.code: [id="cluster-logging-updating-logging_{context}"]
  = Updating cluster logging
  
  After updating the {product-title} cluster, you can update cluster logging from 4.4 to 4.5 by changing the subscription for the Elasticsearch Operator and the Cluster Logging Operator.
  
  When you update:
  
  * You must update the Elasticsearch Operator before updating the Cluster Logging Operator.
  * You must update both the Elasticsearch Operator and the Cluster Logging Operator.
  +
  Kibana is unusable when the Elasticsearch Operator has been updated but the Cluster Logging Operator has not been updated.
  +
  If you update the Cluster Logging Operator before the Elasticsearch Operator, Kibana does not update and the Kibana Custom Resource (CR) is not created. To work around this problem, delete the Cluster Logging Operator Pod. When the Cluster Logging Operator Pod redeploys, the Kibana CR is created.
  
  [IMPORTANT]
  ====
  If your cluster logging version is prior to 4.4, you must upgrade cluster logging to 4.4 before updating to 4.5.
  ====
  
  .Prerequisites
  
  * Update the {product-title} cluster from 4.4 to 4.5.
  
  * Make sure the cluster logging status is healthy:
  +
  