@@ -156,7 +156,7 @@ Cluster Autoscaler
156156Tarmak supports deploying `Cluster Autoscaler
157157<https://github.com/kubernetes/autoscaler/tree/master/cluster-autoscaler> `_ when
158158spinning up a Kubernetes cluster. The following `tarmak.yaml ` snippet shows how
159- you would enable Cluster Autoscaler.
159+ you would enable Cluster Autoscaler.
160160
161161.. code-block :: yaml
162162
@@ -323,9 +323,9 @@ Elasticsearch endpoint and the policy that allow shipping to it:
323323::
324324
325325 Apply complete! Resources: 2 added, 0 changed, 0 destroyed.
326-
326+
327327 Outputs:
328-
328+
329329 elasticsearch_endpoint = search-tarmak-logs-xyz.eu-west-1.es.amazonaws.com
330330 elasticsearch_shipping_policy_arn = arn:aws:iam::1234:policy/tarmak-logs-shipping
331331
@@ -441,29 +441,42 @@ allows to override the deployed version:
441441Prometheus
442442~~~~~~~~~~
443443
444- By default Tarmak will deploy a `Prometheus <https://prometheus.io/ >`_ and some
445- exporters into the ``monitoring `` namespace. Using this config Prometheus could
446- be disabled all together:
444+ By default Tarmak will deploy a `Prometheus <https://prometheus.io/ >`_
445+ installation and some exporters into the ``monitoring `` namespace.
446+
447+ This can be completely disabled with the following cluster configuration:
447448
448449.. code-block :: yaml
449450
450451 kubernetes :
451452 prometheus :
452453 enabled : false
453454
454- Another possibility would be to use The Tarmak provisioned Prometheus only for
455+ Another possibility would be to use the Tarmak provisioned Prometheus only for
455456scraping exporters on instances that are not part of the Kubernetes cluster.
456- Using federation those metrics could then be integrated into an already
457- existing Prometheus deployment. Get that behaviour you needs to set the
458- configuration like that:
457+ Using federation, those metrics could then be integrated into an existing
458+ Prometheus deployment.
459+
460+ To have Prometheus only monitor nodes external to the cluster, use the
461+ following configuration instead:
459462
460463.. code-block :: yaml
461464
462465 kubernetes :
463466 prometheus :
464467 enabled : true
465- externalScrapeTargetsOnly : true
468+ mode : ExternalScrapeTargetsOnly
469+
470+ Finally, you may wish to have Tarmak only install the exporters on the external
471+ nodes. If this is your desired configuration, then set the following mode in
472+ the yaml:
466473
474+ .. code-block :: yaml
475+
476+ kubernetes :
477+ prometheus :
478+ enabled : true
479+ mode : ExternalExportersOnly
467480
468481 API Server
469482~~~~~~~~~~~
0 commit comments