From 7789b55ddd03cea02c9acd3b1dbeeadcd1198185 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 11:59:58 +0200 Subject: [PATCH 01/17] ECK: Document annotations and labels propagation --- .../propagate-labels-annotations.md | 67 +++++++++++++++++++ deploy-manage/toc.yml | 1 + 2 files changed, 68 insertions(+) create mode 100644 deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md new file mode 100644 index 0000000000..8823f1a532 --- /dev/null +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -0,0 +1,67 @@ +--- +mapped_pages: + - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-customize-pods.html +applies_to: + deployment: + eck: all +products: + - id: cloud-kubernetes +--- + +# Propagate Labels and Annotations [k8s-propagate-labels-annotations] + +Starting with version `3.1.0`, Elastic Cloud on Kubernetes (ECK) supports propagating labels and annotations from the parent resource to the child resources it creates. This feature allows you to apply metadata consistently across all resources managed by ECK, such as Elasticsearch, Kibana, APM Server, Agent, and Beats. + +The example below demonstrates how to set up an Elasticsearch cluster with custom labels and annotations that will be propagated to all child resources created by ECK. This can also be applied to Kibana, APM Server, Agent, and Beats resources. + +```yaml +# This sample sets up an Elasticsearch cluster with 3 nodes. +apiVersion: elasticsearch.k8s.elastic.co/v1 +kind: Elasticsearch +metadata: + annotations: + # Some custom annotations to be propagated to resources created by the operator. + my-annotation1: "my-annotation1-value" + my-annotation2: "my-annotation2-value" + # Instructions for the operator to propagate these annotations and labels to resources it creates. + eck.k8s.alpha.elastic.co/propagate-annotations: "my-annotation1, my-annotation2" + eck.k8s.alpha.elastic.co/propagate-labels: "my-label1, my-label2" + labels: + # Some custom labels to be propagated to resources created by the operator. + my-label1: "my-label1-value" + my-label2: "my-label2-value" + name: elasticsearch-sample +spec: + version: 9.0.0 + nodeSets: + - name: default + config: + # this allows ES to run on nodes even if their vm.max_map_count has not been increased, at a performance cost + node.store.allow_mmap: false + count: 1 +``` + +The custom labels and annotations specified in the `metadata` section of the parent resource will be propagated to all child resources created by ECK, such as StatefulSets, Pods, Services, and Secrets. This ensures that all resources have consistent metadata, which can be useful for filtering, monitoring, and managing resources in Kubernetes: + +```sh +kubectl get sts,pods,svc -l my-label1=my-label1-value,my-label2=my-label2-value +``` + +```sh +NAME READY AGE +statefulset.apps/elasticsearch-sample-es-default 1/1 4m10s + +NAME READY STATUS RESTARTS AGE +pod/elasticsearch-sample-es-default-0 1/1 Running 0 4m9s + +NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE +service/elasticsearch-sample-es-default ClusterIP None 9200/TCP 4m12s +service/elasticsearch-sample-es-http ClusterIP XX.XX.XX.XX 9200/TCP 4m14s +service/elasticsearch-sample-es-internal-http ClusterIP XX.XX.XX.XX 9200/TCP 4m14s +service/elasticsearch-sample-es-transport ClusterIP None 9300/TCP 4m14s +``` + +::::{note} +Propagated labels and annotations are not automatically removed when the parent resource is deleted. If you want to remove them, you need to do so manually or use a cleanup script. +:::: + diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index 2002ff21f8..5bd344e89f 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -224,6 +224,7 @@ toc: - file: deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md - file: deploy/cloud-on-k8s/k8s-kibana-plugins.md - file: deploy/cloud-on-k8s/customize-pods.md + - file: deploy/cloud-on-k8s/propagate-annotations-labels.md - file: deploy/cloud-on-k8s/manage-compute-resources.md - file: deploy/cloud-on-k8s/recipes.md - file: deploy/cloud-on-k8s/connect-to-external-elastic-resources.md From 36fba4767124d79c2a93fa798bb9e560e4082229 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 12:04:45 +0200 Subject: [PATCH 02/17] remove mapped pages --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 8823f1a532..4b85e6f758 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -1,6 +1,4 @@ --- -mapped_pages: - - https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-customize-pods.html applies_to: deployment: eck: all From bdfc4a0a8186bac7cb996a30f5105fde54b016a1 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 12:57:25 +0200 Subject: [PATCH 03/17] fix link --- deploy-manage/toc.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index 5bd344e89f..d270932d55 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -224,7 +224,7 @@ toc: - file: deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md - file: deploy/cloud-on-k8s/k8s-kibana-plugins.md - file: deploy/cloud-on-k8s/customize-pods.md - - file: deploy/cloud-on-k8s/propagate-annotations-labels.md + - file: deploy/cloud-on-k8s/propagate-labels-annotations.md - file: deploy/cloud-on-k8s/manage-compute-resources.md - file: deploy/cloud-on-k8s/recipes.md - file: deploy/cloud-on-k8s/connect-to-external-elastic-resources.md From 0e6e75cc50c9149caa44fcc0ab0f7a4f7de400a1 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 13:01:34 +0200 Subject: [PATCH 04/17] Test {version} --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 4b85e6f758..263e90a725 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -30,7 +30,7 @@ metadata: my-label2: "my-label2-value" name: elasticsearch-sample spec: - version: 9.0.0 + version: {version} nodeSets: - name: default config: From dafbf4d160253eb1e47b9950c3ce5dd2e4e777d1 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 13:08:46 +0200 Subject: [PATCH 05/17] Use shortcuts --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 263e90a725..11b0337fe0 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -8,9 +8,9 @@ products: # Propagate Labels and Annotations [k8s-propagate-labels-annotations] -Starting with version `3.1.0`, Elastic Cloud on Kubernetes (ECK) supports propagating labels and annotations from the parent resource to the child resources it creates. This feature allows you to apply metadata consistently across all resources managed by ECK, such as Elasticsearch, Kibana, APM Server, Agent, and Beats. +Starting with version `3.1.0`, Elastic Cloud on Kubernetes (ECK) supports propagating labels and annotations from the parent resource to the child resources it creates. This feature allows you to apply metadata consistently across all resources managed by ECK, such as {{es}}, {{kib}}, {ls}}, {{APM-server-name}}, {{agent}}, and {{beats}}. -The example below demonstrates how to set up an Elasticsearch cluster with custom labels and annotations that will be propagated to all child resources created by ECK. This can also be applied to Kibana, APM Server, Agent, and Beats resources. +The example below demonstrates how to set up an Elasticsearch cluster with custom labels and annotations that will be propagated to all child resources created by ECK. This can also be applied to {{kib}}, {ls}}, {{APM-server-name}}, {{agent}}, and {{beats}} resources. ```yaml # This sample sets up an Elasticsearch cluster with 3 nodes. From 4dc8c7aff7648f5630898164838dbef173dd946f Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 14:03:54 +0200 Subject: [PATCH 06/17] Use eck_resources_list --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 11b0337fe0..7682305889 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -8,9 +8,9 @@ products: # Propagate Labels and Annotations [k8s-propagate-labels-annotations] -Starting with version `3.1.0`, Elastic Cloud on Kubernetes (ECK) supports propagating labels and annotations from the parent resource to the child resources it creates. This feature allows you to apply metadata consistently across all resources managed by ECK, such as {{es}}, {{kib}}, {ls}}, {{APM-server-name}}, {{agent}}, and {{beats}}. +Starting with version `3.1.0`, Elastic Cloud on Kubernetes (ECK) supports propagating labels and annotations from the parent resource to the child resources it creates. This feature allows you to apply metadata consistently across all resources managed by ECK, such as {{eck_resources_list}}. -The example below demonstrates how to set up an Elasticsearch cluster with custom labels and annotations that will be propagated to all child resources created by ECK. This can also be applied to {{kib}}, {ls}}, {{APM-server-name}}, {{agent}}, and {{beats}} resources. +The example below demonstrates how to set up an {{es}} cluster with custom labels and annotations that will be propagated to all child resources created by ECK. As mentioned above, this can be also applied to other resources managed by ECK. ```yaml # This sample sets up an Elasticsearch cluster with 3 nodes. From 595273f828628a223b67d9e0b8d8ade8b45018d0 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 14:14:59 +0200 Subject: [PATCH 07/17] update --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 7682305889..4c63d2ff91 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -8,11 +8,11 @@ products: # Propagate Labels and Annotations [k8s-propagate-labels-annotations] -Starting with version `3.1.0`, Elastic Cloud on Kubernetes (ECK) supports propagating labels and annotations from the parent resource to the child resources it creates. This feature allows you to apply metadata consistently across all resources managed by ECK, such as {{eck_resources_list}}. +Starting with version `3.1.0`, Elastic Cloud on Kubernetes (ECK) supports propagating labels and annotations from the parent resource to the child resources it creates. This can be used on all custom resources managed by ECK, such as {{eck_resources_list}}. The example below demonstrates how to set up an {{es}} cluster with custom labels and annotations that will be propagated to all child resources created by ECK. As mentioned above, this can be also applied to other resources managed by ECK. -```yaml +```yaml subs=true # This sample sets up an Elasticsearch cluster with 3 nodes. apiVersion: elasticsearch.k8s.elastic.co/v1 kind: Elasticsearch From 3a41137deb72f73db66d8d284fa4218372c29994 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 14:18:31 +0200 Subject: [PATCH 08/17] wording --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 4c63d2ff91..3a09d3fb7e 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -10,7 +10,7 @@ products: Starting with version `3.1.0`, Elastic Cloud on Kubernetes (ECK) supports propagating labels and annotations from the parent resource to the child resources it creates. This can be used on all custom resources managed by ECK, such as {{eck_resources_list}}. -The example below demonstrates how to set up an {{es}} cluster with custom labels and annotations that will be propagated to all child resources created by ECK. As mentioned above, this can be also applied to other resources managed by ECK. +The example below demonstrates how to use this feature on a {{es}} cluster, however, as mentioned above, this can be also applied to any custom resource managed by ECK. ```yaml subs=true # This sample sets up an Elasticsearch cluster with 3 nodes. From eb43c3d87fe19efb009f740d3fa4edf89173e7c1 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 14:26:23 +0200 Subject: [PATCH 09/17] mention * and restrictions --- .../propagate-labels-annotations.md | 27 +++++++++++++++++-- 1 file changed, 25 insertions(+), 2 deletions(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 3a09d3fb7e..39df041c2c 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -59,7 +59,30 @@ service/elasticsearch-sample-es-internal-http ClusterIP XX.XX.XX.XX 9300/TCP 4m14s ``` +It is possible to use `*` as a wildcard to propagate all labels and annotations from the parent resource to the child resources. For example: + +```yaml subs=true +# This sample sets up an Elasticsearch cluster with 3 nodes. +apiVersion: elasticsearch.k8s.elastic.co/v1 +kind: Elasticsearch +metadata: + annotations: + # Instructions for the operator to propagate all the annotations and labels to resources it creates. + eck.k8s.alpha.elastic.co/propagate-annotations: "*" + eck.k8s.alpha.elastic.co/propagate-labels: "*" + name: elasticsearch-sample +spec: + version: {version} + nodeSets: + - name: default + config: + # this allows ES to run on nodes even if their vm.max_map_count has not been increased, at a performance cost + node.store.allow_mmap: false + count: 1 +``` + ::::{note} -Propagated labels and annotations are not automatically removed when the parent resource is deleted. If you want to remove them, you need to do so manually or use a cleanup script. +Please be aware of the following considerations when using this feature: +* Propagated labels and annotations are not automatically removed when the parent resource is deleted. If you want to remove them, you need to do so manually or use a cleanup script. +* To prevent conflicts, some labels and annotations reserved for internal use by ECK or Kubernetes, are not propagated. This is the case for labels and annotations that start with `eck.k8s.alpha.elastic.co/`, `k8s.elastic.co/` and also `kubectl.kubernetes.io/last-applied-configuration`. :::: - From 2a0629bdd653913d54aa45b99b21139d662c880d Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 14:34:24 +0200 Subject: [PATCH 10/17] fix --- .../cloud-on-k8s/propagate-labels-annotations.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 39df041c2c..8edec30964 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -30,7 +30,7 @@ metadata: my-label2: "my-label2-value" name: elasticsearch-sample spec: - version: {version} + version: 9.1.0 nodeSets: - name: default config: @@ -61,7 +61,7 @@ service/elasticsearch-sample-es-transport ClusterIP None Date: Wed, 16 Jul 2025 14:40:15 +0200 Subject: [PATCH 11/17] fix comment --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 8edec30964..1c6eab0361 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -12,8 +12,7 @@ Starting with version `3.1.0`, Elastic Cloud on Kubernetes (ECK) supports propag The example below demonstrates how to use this feature on a {{es}} cluster, however, as mentioned above, this can be also applied to any custom resource managed by ECK. -```yaml subs=true -# This sample sets up an Elasticsearch cluster with 3 nodes. +```yaml apiVersion: elasticsearch.k8s.elastic.co/v1 kind: Elasticsearch metadata: @@ -62,7 +61,6 @@ service/elasticsearch-sample-es-transport ClusterIP None Date: Wed, 16 Jul 2025 14:48:20 +0200 Subject: [PATCH 12/17] Use {{eck}} --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 1c6eab0361..de5cf984d1 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -8,9 +8,9 @@ products: # Propagate Labels and Annotations [k8s-propagate-labels-annotations] -Starting with version `3.1.0`, Elastic Cloud on Kubernetes (ECK) supports propagating labels and annotations from the parent resource to the child resources it creates. This can be used on all custom resources managed by ECK, such as {{eck_resources_list}}. +Starting with version `3.1.0`,{{eck}} supports propagating labels and annotations from the parent resource to the child resources it creates. This can be used on all custom resources managed by ECK, such as {{eck_resources_list}}. -The example below demonstrates how to use this feature on a {{es}} cluster, however, as mentioned above, this can be also applied to any custom resource managed by ECK. +The example below demonstrates how to use this feature on a {{es}} cluster, however, as mentioned above, this can be also applied to any custom resource managed by {{eck}}. ```yaml apiVersion: elasticsearch.k8s.elastic.co/v1 @@ -38,7 +38,7 @@ spec: count: 1 ``` -The custom labels and annotations specified in the `metadata` section of the parent resource will be propagated to all child resources created by ECK, such as StatefulSets, Pods, Services, and Secrets. This ensures that all resources have consistent metadata, which can be useful for filtering, monitoring, and managing resources in Kubernetes: +The custom labels and annotations specified in the `metadata` section of the parent resource will be propagated to all child resources created by {{eck}}, such as StatefulSets, Pods, Services, and Secrets. This ensures that all resources have consistent metadata, which can be useful for filtering, monitoring, and managing resources in Kubernetes: ```sh kubectl get sts,pods,svc -l my-label1=my-label1-value,my-label2=my-label2-value From 118f320fdfcfd997d9fa57394548edb7144f61c6 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 14:50:35 +0200 Subject: [PATCH 13/17] space --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index de5cf984d1..37490bfb62 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -8,7 +8,7 @@ products: # Propagate Labels and Annotations [k8s-propagate-labels-annotations] -Starting with version `3.1.0`,{{eck}} supports propagating labels and annotations from the parent resource to the child resources it creates. This can be used on all custom resources managed by ECK, such as {{eck_resources_list}}. +Starting with version `3.1.0`, {{eck}} supports propagating labels and annotations from the parent resource to the child resources it creates. This can be used on all custom resources managed by ECK, such as {{eck_resources_list}}. The example below demonstrates how to use this feature on a {{es}} cluster, however, as mentioned above, this can be also applied to any custom resource managed by {{eck}}. From e0973bc9157c439bfac61821e4a558aa8bc4767b Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 20:03:42 +0200 Subject: [PATCH 14/17] Update deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 37490bfb62..a30d9c4e55 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -82,5 +82,5 @@ spec: ::::{note} Please be aware of the following considerations when using this feature: * Propagated labels and annotations are not automatically deleted. If you want to remove them from the child resources, you need to do so manually or use a cleanup script. -* To prevent conflicts, some labels and annotations reserved for internal use by ECK or Kubernetes, are not propagated. This is the case for labels and annotations that match `*.k8s.*.elastic.co/` and also `kubectl.kubernetes.io/last-applied-configuration`. +* To prevent conflicts, some labels and annotations reserved for internal use by ECK or Kubernetes are not propagated. This is the case for labels and annotations that match `*.k8s.*.elastic.co/` and also `kubectl.kubernetes.io/last-applied-configuration`. :::: From b772c74cfb4927de6213d13e3d0a637caca99c90 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Wed, 16 Jul 2025 20:04:03 +0200 Subject: [PATCH 15/17] Update deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index a30d9c4e55..525d2727de 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -80,7 +80,7 @@ spec: ``` ::::{note} -Please be aware of the following considerations when using this feature: +Note the following considerations when using this feature: * Propagated labels and annotations are not automatically deleted. If you want to remove them from the child resources, you need to do so manually or use a cleanup script. * To prevent conflicts, some labels and annotations reserved for internal use by ECK or Kubernetes are not propagated. This is the case for labels and annotations that match `*.k8s.*.elastic.co/` and also `kubectl.kubernetes.io/last-applied-configuration`. :::: From 2f8eb1bd7c875b62cc329ff5db4acde021a70ba9 Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Thu, 17 Jul 2025 08:04:15 +0200 Subject: [PATCH 16/17] Update deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md Co-authored-by: shainaraskas <58563081+shainaraskas@users.noreply.github.com> --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 525d2727de..4d9a8de97b 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -1,7 +1,7 @@ --- applies_to: deployment: - eck: all + eck: 3.1.0 products: - id: cloud-kubernetes --- From d2b0898e2bdd7613a0336caab8c2c0d502ce271a Mon Sep 17 00:00:00 2001 From: Michael Morello Date: Thu, 17 Jul 2025 08:12:57 +0200 Subject: [PATCH 17/17] Attempt to fix version --- .../deploy/cloud-on-k8s/propagate-labels-annotations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md index 4d9a8de97b..e4c0486c72 100644 --- a/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md +++ b/deploy-manage/deploy/cloud-on-k8s/propagate-labels-annotations.md @@ -1,7 +1,7 @@ --- applies_to: deployment: - eck: 3.1.0 + eck: preview 3.1 products: - id: cloud-kubernetes ---