From 630a034fe2c76b4651f7bcb3e7b8a7d7f00c5fe2 Mon Sep 17 00:00:00 2001 From: kmetin Date: Wed, 26 Jun 2024 15:57:18 +0300 Subject: [PATCH 1/3] add create license step --- .../hazelcast-platform-operator-expose-externally.adoc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/modules/ROOT/pages/hazelcast-platform-operator-expose-externally.adoc b/docs/modules/ROOT/pages/hazelcast-platform-operator-expose-externally.adoc index c860b95..6b10710 100644 --- a/docs/modules/ROOT/pages/hazelcast-platform-operator-expose-externally.adoc +++ b/docs/modules/ROOT/pages/hazelcast-platform-operator-expose-externally.adoc @@ -17,6 +17,14 @@ * Up and running https://kubernetes.io/[Kubernetes] cluster * Kubernetes command-line tool, https://kubernetes.io/docs/tasks/tools/#kubectl[kubectl] * Deployed xref:operator:ROOT:get-started.adoc[Hazelcast Platform Operator] +* Create a license secret: ++ +Create a secret with your link:http://trialrequest.hazelcast.com/[Hazelcast Enterprise License]. ++ +[source, shell] +---- +kubectl create secret generic hazelcast-license-key --from-literal=license-key= +---- WARNING: This tutorial uses LoadBalancer services to connect to Hazelcast from outside of the Kubernetes cluster. Therefore, it is essential to ensure that your Kubernetes cluster can assign public IPs to LoadBalancer services. This is particularly important if you are using a local Kubernetes cluster such as Minikube or Kind. From c057fb01bab3eed5646e3723fbd866e8b4f5d9f0 Mon Sep 17 00:00:00 2001 From: kmetin Date: Wed, 26 Jun 2024 16:06:02 +0300 Subject: [PATCH 2/3] add licenseKeySecretName to examples --- .../examples/operator-expose-externally/hazelcast-unisocket.yaml | 1 + .../ROOT/examples/operator-expose-externally/hazelcast.yaml | 1 + 2 files changed, 2 insertions(+) diff --git a/docs/modules/ROOT/examples/operator-expose-externally/hazelcast-unisocket.yaml b/docs/modules/ROOT/examples/operator-expose-externally/hazelcast-unisocket.yaml index c5618f6..e065f06 100644 --- a/docs/modules/ROOT/examples/operator-expose-externally/hazelcast-unisocket.yaml +++ b/docs/modules/ROOT/examples/operator-expose-externally/hazelcast-unisocket.yaml @@ -3,6 +3,7 @@ kind: Hazelcast metadata: name: my-hazelcast-unisocket spec: + licenseKeySecretName: hazelcast-license-key exposeExternally: type: Unisocket discoveryServiceType: LoadBalancer diff --git a/docs/modules/ROOT/examples/operator-expose-externally/hazelcast.yaml b/docs/modules/ROOT/examples/operator-expose-externally/hazelcast.yaml index d1db77d..76a888a 100644 --- a/docs/modules/ROOT/examples/operator-expose-externally/hazelcast.yaml +++ b/docs/modules/ROOT/examples/operator-expose-externally/hazelcast.yaml @@ -3,6 +3,7 @@ kind: Hazelcast metadata: name: my-hazelcast spec: + licenseKeySecretName: hazelcast-license-key exposeExternally: type: Smart discoveryServiceType: LoadBalancer From 12999fd03b2ff37a9c1a663d0074ed61c7e6645b Mon Sep 17 00:00:00 2001 From: kmetin Date: Tue, 2 Jul 2024 10:54:15 +0300 Subject: [PATCH 3/3] fix PR comment --- .../pages/hazelcast-platform-operator-expose-externally.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/modules/ROOT/pages/hazelcast-platform-operator-expose-externally.adoc b/docs/modules/ROOT/pages/hazelcast-platform-operator-expose-externally.adoc index 6b10710..4cee9a6 100644 --- a/docs/modules/ROOT/pages/hazelcast-platform-operator-expose-externally.adoc +++ b/docs/modules/ROOT/pages/hazelcast-platform-operator-expose-externally.adoc @@ -20,12 +20,15 @@ * Create a license secret: + Create a secret with your link:http://trialrequest.hazelcast.com/[Hazelcast Enterprise License]. + + [source, shell] ---- kubectl create secret generic hazelcast-license-key --from-literal=license-key= ---- +NOTE: Starting with version 5.13, Hazelcast Platform Operator only supports Hazelcast Enterprise cluster creation. Even the feature can be used in Hazelcast Open Source clusters, Hazelcast Platform Operator requires license key to run a cluster. + WARNING: This tutorial uses LoadBalancer services to connect to Hazelcast from outside of the Kubernetes cluster. Therefore, it is essential to ensure that your Kubernetes cluster can assign public IPs to LoadBalancer services. This is particularly important if you are using a local Kubernetes cluster such as Minikube or Kind. == Introduction