Merge pull request #167 from wjimenez5271/patch-1

#166 - clarify how service names are generated
upmc-enterprises · Apr 26, 2018 · 31eae2d · 31eae2d
2 parents 5ad47a5 + dfde444
commit 31eae2d
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/README.md b/README.md
@@ -248,7 +248,7 @@ spec:
 
 # Access Cluster
 
-Once deployed and all pods are running, the cluster can be accessed internally via `https://elasticsearch:9200/` or `https://${ELASTICSEARCH_SERVICE_HOST}:9200/`
+Once deployed and all pods are running, the cluster can be accessed internally via https://elasticsearch:9200/ or https://${ELASTICSEARCH_SERVICE_HOST}:9200/. **Note**: the service name for the ES client may also be "elasticsearch + <cluster-Name>" as defined in your `ElasticsearchCluster` resource.
 
 ![alt text](docs/images/running-cluster.png "Running Cluster")