[CN-1382]: Docs for Lite Members

docs/modules/ROOT/examples/lite-member-jvm.yaml

@@ -0,0 +1,15 @@
+apiVersion: hazelcast.com/v1alpha1
+kind: Hazelcast
+metadata:
+  name: hazelcast
+spec:
+  repository: 'docker.io/hazelcast/hazelcast-enterprise'
+  licenseKeySecretName: hazelcast-license-key
+  clusterSize: 3
+  liteMember:
+    count: 2
+    jvm:
+      memory:
+        initialRAMPercentage: "10"
+        maxRAMPercentage: "20"
+        minRAMPercentage: "10"

docs/modules/ROOT/examples/lite-member-resource-limits.yaml

@@ -0,0 +1,17 @@
+apiVersion: hazelcast.com/v1alpha1
+kind: Hazelcast
+metadata:
+  name: hazelcast
+spec:
+  repository: 'docker.io/hazelcast/hazelcast-enterprise'
+  licenseKeySecretName: hazelcast-license-key
+  clusterSize: 3
+  liteMember:
+    count: 2
+    resources:
+      requests:
+        memory: "64Mi"
+        cpu: "250m"
+      limits:
+        memory: "128Mi"
+        cpu: "500m"

docs/modules/ROOT/examples/lite-member-scheduling.yaml

@@ -0,0 +1,13 @@
+apiVersion: hazelcast.com/v1alpha1
+kind: Hazelcast
+metadata:
+  name: hazelcast
+spec:
+  repository: 'docker.io/hazelcast/hazelcast-enterprise'
+  licenseKeySecretName: hazelcast-license-key
+  clusterSize: 3
+  liteMember:
+    count: 2
+    scheduling:
+      nodeSelector:
+        topology.kubernetes.io/region: us-west1

docs/modules/ROOT/examples/lite-member.yaml

@@ -0,0 +1,10 @@
+apiVersion: hazelcast.com/v1alpha1
+kind: Hazelcast
+metadata:
+  name: hazelcast
+spec:
+  repository: 'docker.io/hazelcast/hazelcast-enterprise'
+  licenseKeySecretName: hazelcast-license-key
+  clusterSize: 3
+  liteMember:
+    count: 2

docs/modules/ROOT/nav.adoc

@@ -6,6 +6,7 @@
 * xref:scheduling-configuration.adoc[Scheduling Hazelcast Pods]
 * xref:serialization-configuration.adoc[Serialization]
 * xref:scaling-upgrading.adoc[Scaling & Upgrading]
+* xref:lite-members.adoc[Deploying Lite Members]
 * xref:cp-subsystem.adoc[Enabling CP Subsystem]
 * xref:tiered-storage.adoc[Tiered Storage]
 * Configuring Data Structures

docs/modules/ROOT/pages/lite-members.adoc

@@ -0,0 +1,55 @@
+= Deploying Lite Members
+
+You can the Hazelcast Platform Operator to deploy link:https://docs.hazelcast.com/hazelcast/latest/maintain-cluster/lite-members[Lite Members]. You can use the separate `liteMember` section in the Hazelcast CR.
+
+WARNING: When `jvm`, `env`, `resources`, `scheduling` sections are configured in the Hazelcast CR, it will not affect the lite member configuration. Lite members must be configured as explained in the next sections in this document.
+
+== Configuring the Number of Lite Members
+
+To configure the number of lite members you want to deploy in the Hazelcast CR, use the `count` field in the `liteMember` section of the Hazelcast CR.
+
+.Example Lite Member Count Configuration
+[source,yaml,subs="attributes+"]
+----
+include::ROOT:example$/lite-member.yaml[]
+----
+
+When you apply the given example, 3 data members and 2 lite members are going to be deployed.
+
+NOTE: As seen in the example, `clusterSize` stands for the number of data members to be created.
+
+== Configuring JVM Parameters
+
+To configure JVM Parameters specifically for lite members, you can use the `jvm` field in the `liteMember` section of the Hazelcast CR.
+
+.Example Lite Member JVM Configuration
+[source,yaml,subs="attributes+"]
+----
+include::ROOT:example$/lite-member-jvm.yaml[]
+----
+
+== Configuring Environment Variables
+
+To configure environment variables specifically for lite members, you can use the `env` field in the `liteMember` section of the Hazelcast CR.
+
+Same rules and logic is applicable as in the xref:env-vars.adoc[Environment variables].
+
+== Configuring Resource Limits
+
+To configure resource limits specifically for lite members, you can use the `resources` field in the `liteMember` section of the Hazelcast CR.
+
+.Example Lite Member Resource Limits Configuration
+[source,yaml,subs="attributes+"]
+----
+include::ROOT:example$/lite-member-resource-limits.yaml[]
+----
+
+== Configuring Scheduling
+
+To configure scheduling specifically for lite members, you can use the `scheduling` field in the `liteMember` section of the Hazelcast CR.
+
+.Example Lite Member Scheduling Configuration
+[source,yaml,subs="attributes+"]
+----
+include::ROOT:example$/lite-member-scheduling.yaml[]
+----