From e0098783263da090bea03a3b2e10f4d85c2d25d5 Mon Sep 17 00:00:00 2001 From: Kuni Sen Date: Mon, 1 Sep 2025 10:39:46 +0900 Subject: [PATCH 1/3] Clarify ECK license update --- deploy-manage/license/manage-your-license-in-eck.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/deploy-manage/license/manage-your-license-in-eck.md b/deploy-manage/license/manage-your-license-in-eck.md index fd26cb62bd..e8edd233d7 100644 --- a/deploy-manage/license/manage-your-license-in-eck.md +++ b/deploy-manage/license/manage-your-license-in-eck.md @@ -107,10 +107,18 @@ Before your current Enterprise license expires, you will receive a new Enterpris You can check the expiry date of your license in the [elastic-licensing](#k8s-get-usage-data) ConfigMap. Enterprise licenses are container licenses that include multiple licenses for individual {{es}} clusters with shorter expiry. Therefore, you get a different expiry in {{kib}} or through the {{es}} [`_license`](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-license-get) API. ECK automatically updates the {{es}} cluster licenses until the expiry date of the ECK Enterprise license is reached. :::: +::::{important} +To avoid any unintended downgrade of individual {{es}} clusters to a Basic license while installing the new license, we recommend installing the new Enterprise license as a new Kubernetes secret next to your existing Enterprise license. +:::: + +To update your license, please refer to the [Add a license](#k8s-add-license.md) documentation and utilize a different Kubernetes secret name for your new license. For instance: -To avoid any unintended downgrade of individual {{es}} clusters to a Basic license while installing the new license, we recommend installing the new Enterprise license as a new Kubernetes secret next to your existing Enterprise license. Just replace `eck-license` with a different name in the [Kubernetes secret example](#k8s-add-license). ECK will use the correct license automatically. +```shell +kubectl create secret generic eck-license-new --from-file= -n elastic-system +kubectl label secret eck-license-new "license.k8s.elastic.co/scope"=operator -n elastic-system +``` -Once you have created the new license secret you can safely delete the old license secret. +After creating the new license secret, you can follow the [Get usage data](#k8s-get-usage-data.md) guide to verify the status of your new license. For example, ensure that the `eck_license_expiry_date` reflects the expiration date of your new license. Once the new license is confirmed, you may safely delete the old license secret. ## Get usage data [k8s-get-usage-data] From 2ee12106c8c97801deac7778f230bd87385a1c4b Mon Sep 17 00:00:00 2001 From: Kuni Sen Date: Mon, 1 Sep 2025 12:10:03 +0900 Subject: [PATCH 2/3] Update manage-your-license-in-eck.md --- deploy-manage/license/manage-your-license-in-eck.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/license/manage-your-license-in-eck.md b/deploy-manage/license/manage-your-license-in-eck.md index e8edd233d7..60643dad96 100644 --- a/deploy-manage/license/manage-your-license-in-eck.md +++ b/deploy-manage/license/manage-your-license-in-eck.md @@ -111,14 +111,14 @@ You can check the expiry date of your license in the [elastic-licensing](#k8s-ge To avoid any unintended downgrade of individual {{es}} clusters to a Basic license while installing the new license, we recommend installing the new Enterprise license as a new Kubernetes secret next to your existing Enterprise license. :::: -To update your license, please refer to the [Add a license](#k8s-add-license.md) documentation and utilize a different Kubernetes secret name for your new license. For instance: +To update your license, please refer to the [Add a license](#k8s-add-license) documentation and utilize a different Kubernetes secret name for your new license. For instance: ```shell kubectl create secret generic eck-license-new --from-file= -n elastic-system kubectl label secret eck-license-new "license.k8s.elastic.co/scope"=operator -n elastic-system ``` -After creating the new license secret, you can follow the [Get usage data](#k8s-get-usage-data.md) guide to verify the status of your new license. For example, ensure that the `eck_license_expiry_date` reflects the expiration date of your new license. Once the new license is confirmed, you may safely delete the old license secret. +After creating the new license secret, you can follow the [Get usage data](#k8s-get-usage-data) guide to verify the status of your new license. For example, ensure that the `eck_license_expiry_date` reflects the expiration date of your new license. Once the new license is confirmed, you may safely delete the old license secret. ## Get usage data [k8s-get-usage-data] From 46f38df2022afa9d2b40e47fb98392006f3f5ee7 Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Tue, 2 Sep 2025 17:08:02 +0900 Subject: [PATCH 3/3] Update deploy-manage/license/manage-your-license-in-eck.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/license/manage-your-license-in-eck.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/deploy-manage/license/manage-your-license-in-eck.md b/deploy-manage/license/manage-your-license-in-eck.md index 60643dad96..c9ce087767 100644 --- a/deploy-manage/license/manage-your-license-in-eck.md +++ b/deploy-manage/license/manage-your-license-in-eck.md @@ -118,7 +118,9 @@ kubectl create secret generic eck-license-new --from-file=