From e4bf9406734cebce46eb9baf36c5680fa266b6bd Mon Sep 17 00:00:00 2001 From: Lara Moreno <49395637+laraMorenoIgle@users.noreply.github.com> Date: Thu, 8 May 2025 09:33:58 +0200 Subject: [PATCH 1/4] Update eck-stack-monitoring.md The example for "Connect to an external monitoring elasticsearch cluster" can lead to confusion or seem to be incorrect, so I added a small explanation about what the config in the example does --- .../monitor/stack-monitoring/eck-stack-monitoring.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md index 1878ef7fa2..76b6dd94a7 100644 --- a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md @@ -116,7 +116,9 @@ If Logs stack monitoring is configured for a Beat, and custom container argument ## Connect to an external monitoring {{es}} cluster [k8s_connect_to_an_external_monitoring_elasticsearch_cluster] -If you want to connect to a monitoring {{es}} cluster not managed by ECK, you can reference a Secret instead of an {{es}} cluster in the `monitoring` section through the `secretName` attribute: +If you want to connect to a monitoring {{es}} cluster not managed by ECK, you can reference a Secret instead of an {{es}} cluster in the `monitoring` section through the `secretName` attribute. + +Next example sends cluster metrics to a remote monitoring cluster not managed by ECK, whereas cluster logs are sent to a remote cluster handled by ECK. ```yaml apiVersion: elasticsearch.k8s.elastic.co/v1 @@ -193,4 +195,4 @@ spec: - name: filebeat env: - foo: bar -``` \ No newline at end of file +``` From d2729f7976f24a825433970b90e3644529f11628 Mon Sep 17 00:00:00 2001 From: Lara Moreno <49395637+laraMorenoIgle@users.noreply.github.com> Date: Thu, 8 May 2025 09:45:53 +0200 Subject: [PATCH 2/4] Update deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Edu González de la Herrán <25320357+eedugon@users.noreply.github.com> --- deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md index 76b6dd94a7..b213594353 100644 --- a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md @@ -118,7 +118,7 @@ If Logs stack monitoring is configured for a Beat, and custom container argument If you want to connect to a monitoring {{es}} cluster not managed by ECK, you can reference a Secret instead of an {{es}} cluster in the `monitoring` section through the `secretName` attribute. -Next example sends cluster metrics to a remote monitoring cluster not managed by ECK, whereas cluster logs are sent to a remote cluster handled by ECK. +The next example sends cluster metrics to a remote monitoring cluster not managed by ECK, whereas cluster logs are sent to a remote cluster handled by ECK: ```yaml apiVersion: elasticsearch.k8s.elastic.co/v1 From bfc27b48d0e73a38e081a9daf254b9320a1eeedc Mon Sep 17 00:00:00 2001 From: Lara Moreno <49395637+laraMorenoIgle@users.noreply.github.com> Date: Thu, 8 May 2025 09:50:53 +0200 Subject: [PATCH 3/4] Update eck-stack-monitoring.md Small clarification on the example to send monitoring data to another monitoring cluster --- deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md index b213594353..4410867cdb 100644 --- a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md @@ -145,7 +145,7 @@ spec: ``` 1. The `secretName` and `name` attributes are mutually exclusive, you have to choose one or the other. -2. The `namespace` and `serviceName` attributes can only be used in conjunction with `name`, not with `secretName`. +2. The `namespace` and `serviceName` attributes can only be used in conjunction with `name`, not with `secretName` and only to reference clusters managed by the same ECK instance. The referenced Secret must contain the following connection information: From 156721ccd2601b7461ea0f5249d66cdd68be1a0d Mon Sep 17 00:00:00 2001 From: Lara Moreno <49395637+laraMorenoIgle@users.noreply.github.com> Date: Thu, 8 May 2025 09:57:14 +0200 Subject: [PATCH 4/4] Update deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Edu González de la Herrán <25320357+eedugon@users.noreply.github.com> --- deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md index 4410867cdb..31aa948cda 100644 --- a/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md +++ b/deploy-manage/monitor/stack-monitoring/eck-stack-monitoring.md @@ -145,7 +145,7 @@ spec: ``` 1. The `secretName` and `name` attributes are mutually exclusive, you have to choose one or the other. -2. The `namespace` and `serviceName` attributes can only be used in conjunction with `name`, not with `secretName` and only to reference clusters managed by the same ECK instance. +2. The `namespace` and `serviceName` attributes can only be used in conjunction with `name`, not with `secretName`, and only to reference clusters managed by the same ECK instance. The referenced Secret must contain the following connection information: