Deploying Lite Members

Use the Hazelcast Platform Operator to deploy Lite Members. You can use the separate liteMember section in the Hazelcast CR.

Test change

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 following sections.

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

yaml

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

When you apply the given example, 3 data members and 2 lite members are deployed.

note

As seen in the example, clusterSize represents 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

yaml

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"

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 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

yaml

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"

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

yaml

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