Skip to content

Commit 15907bd

Browse files
kuniseneedugon
andauthored
Clarify ECK license update doc (#2766)
to address #2765 --------- Co-authored-by: Edu González de la Herrán <[email protected]>
1 parent 1219e69 commit 15907bd

File tree

1 file changed

+12
-2
lines changed

1 file changed

+12
-2
lines changed

deploy-manage/license/manage-your-license-in-eck.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -107,10 +107,20 @@ Before your current Enterprise license expires, you will receive a new Enterpris
107107
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.
108108
::::
109109

110+
::::{important}
111+
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.
112+
::::
113+
114+
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:
115+
116+
```shell
117+
kubectl create secret generic eck-license-new --from-file=<path/to/your/new/license.json> -n elastic-system
118+
kubectl label secret eck-license-new "license.k8s.elastic.co/scope"=operator -n elastic-system
119+
```
110120

111-
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.
121+
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.
112122

113-
Once you have created the new license secret you can safely delete the old license secret.
123+
Once the new license is confirmed, you may safely delete the old license secret.
114124

115125

116126
## Get usage data [k8s-get-usage-data]

0 commit comments

Comments
 (0)