diff --git a/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md b/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md
index 9931bab209..8a534b0bd5 100644
--- a/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md
+++ b/docs/tasks/debug-application-cluster/logging-elasticsearch-kibana.md
@@ -12,7 +12,9 @@ in the [Logging With Stackdriver Logging](/docs/user-guide/logging/stackdriver).
 This article describes how to set up a cluster to ingest logs into
 [Elasticsearch](https://www.elastic.co/products/elasticsearch), and view
 them using [Kibana](https://www.elastic.co/products/kibana), as an alternative to
-Stackdriver Logging when running on GCE. Note that Elasticsearch and Kibana do not work with Kubernetes clusters hosted on Google Container Engine.
+Stackdriver Logging when running on GCE. Note that Elasticsearch and Kibana
+cannot be set up automatically in the Kubernetes cluster hosted on
+Google Container Engine, you have to deploy it manually.
 
 To use Elasticsearch and Kibana for cluster logging, you should set the
 following environment variable as shown below when creating your cluster with