From cbaaf48a7d1166aac40ce448cef3c2d182758be3 Mon Sep 17 00:00:00 2001 From: Richard Panek Date: Mon, 22 Jan 2018 15:32:28 -0700 Subject: [PATCH] Clarifies exception in naming env vars regarding clusters --- readme.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/readme.md b/readme.md index adcb40f..d8ce5a2 100644 --- a/readme.md +++ b/readme.md @@ -72,6 +72,10 @@ Example: For creating the url to each individual hystrix stream, turbine is using the instance ip and appends a suffix specified by the ``turbine.instanceUrlSuffix``. To configure this property via env variable you just need to set an environment variable with name ``TURBINE_INSTANCEURLSUFFIX``. +For specifying which application(s) that will belong to a cluster with the ``turbine.aggregator.clusters.`` configuration property, + you set the environment variable as ``TURBINE_AGGREGATOR_CLUSTERS_``. Note that the case of ```` must match how it + is specified with ``TURBINE_AGGREGATOR_CLUSTERCONFIG``. + #### Using ConfigMap The turbine server is powered by [Spring Cloud Kubernetes](https://github.com/fabric8io/spring-cloud-kubernetes) which among other allows you to externalize your ``application.yml`` in a [ConfigMap](http://kubernetes.io/docs/user-guide/configmap/). @@ -101,7 +105,7 @@ or if we would like **all** service of the ``foo`` namespace: turbine.aggregator.clusters.example=foo.* -Note, that the option can be also provided as environment variables (e.g. TURBINE_AGGREGATOR_CLUSTER_FOO) or even via ConfigMap as described above. +Note, that the option can be also provided as environment variables (e.g. ``TURBINE_AGGREGATOR_CLUSTER_example``) or even via ConfigMap as described above. ## Ribbon Discovery