Skip to content

Clarify ECK license update doc #2766

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Clarify ECK license update doc #2766

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e009878
Clarify ECK license update
kunisen Sep 1, 2025
2ee1210
Update manage-your-license-in-eck.md
kunisen Sep 1, 2025
46f38df
Update deploy-manage/license/manage-your-license-in-eck.md
kunisen Sep 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions deploy-manage/license/manage-your-license-in-eck.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,10 +107,20 @@ 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) documentation and utilize a different Kubernetes secret name for your new license. For instance:

```shell
kubectl create secret generic eck-license-new --from-file=<path/to/your/new/license.json> -n elastic-system
kubectl label secret eck-license-new "license.k8s.elastic.co/scope"=operator -n elastic-system
```

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.
After creating the new license, verify its status as described in [Get usage data](#k8s-get-usage-data). For example, ensure that the `eck_license_expiry_date` reflects the expiration date of your new license.

Once you have created the new license secret you can safely delete the old license secret.
Once the new license is confirmed, you may safely delete the old license secret.


## Get usage data [k8s-get-usage-data]
Expand Down
Loading