Chapter 7. Setting up Data Grid services

Procedure

1. Create an Infinispan CR that sets spec.service.type: DataGrid and configures any other Data Grid service resources.

   apiVersion: infinispan.org/v1
   kind: Infinispan
   metadata:
     name: infinispan
   spec:
     replicas: 2
     version: <Data Grid_version>
     service:
       type: DataGrid

   Important

   You cannot change the spec.service.type field after you create pods. To change the service type, you must delete the existing pods and create new ones.

2. Apply your Infinispan CR to create the cluster.

Procedure

1. Allocate storage resources with the spec.service.container.storage field.

2. Configure either the ephemeralStorage field or the storageClassName field as required.

   Note

   These fields are mutually exclusive. Add only one of them to your Infinispan CR.

3. Apply the changes.

Procedure

1. Allocate the number of CPU units with the spec.container.cpu field.

2. Allocate the amount of memory, in bytes, with the spec.container.memory field.

   The cpu and memory fields have values in the format of <limit>:<requests>. For example, cpu: "2000m:1000m" limits pods to a maximum of 2000m of CPU and requests 1000m of CPU for each pod at startup. Specifying a single value sets both the limit and request.

3. Apply your Infinispan CR.

   If your cluster is running, Data Grid Operator restarts the Data Grid pods so changes take effect.

Procedure

1. Configure JVM options with the spec.container filed in your Infinispan CR.

2. Apply your Infinispan CR.

   If your cluster is running, Data Grid Operator restarts the Data Grid pods so changes take effect.

Procedure

1. Configure probe values using the spec.service.container.*Probe fields:

   spec:
     service:
       container:
         readinessProbe:
           failureThreshold: 1
           initialDelaySeconds: 1
           periodSeconds: 1
           successThreshold: 1
           timeoutSeconds: 1
         livenessProbe:
           failureThreshold: 1
           initialDelaySeconds: 1
           periodSeconds: 1
           successThreshold: 1
           timeoutSeconds: 1
         startupProbe:
           failureThreshold: 1
           initialDelaySeconds: 1
           periodSeconds: 1
           successThreshold: 1
           timeoutSeconds: 1

   Important

   If no value is specified for a given probe value, then the Data Grid Operator default is used.

2. Apply your Infinispan CR.

   If your cluster is running, Data Grid Operator restarts the Data Grid pods in order for the changes to take effect.

Procedure

1. Define a PriorityClass object by specifying its name and value.

   high-priority.yaml

   apiVersion: scheduling.k8s.io/v1
   kind: PriorityClass
   metadata:
     name: high-priority
   value: 1000000
   globalDefault: false
   description: "Use this priority class for high priority service pods only."

2. Create the priority class.

   oc create -f high-priority.yaml

3. Reference the priority class name in the pod configuration.

   Infinispan CR

   kind: Infinispan
   ...
   spec:
     scheduling:
       affinity:
         ...
       priorityClassName: "high-priority"
       ...

   You must reference an existing priority class name, otherwise the pod is rejected.

4. Apply the changes.

Procedure

1. Configure Data Grid logging with the spec.logging.pattern field in your Infinispan CR.

   spec:
     logging:
       pattern: %X{address} %X{user} [%d{dd/MMM/yyyy:HH:mm:ss Z}]

2. Apply the changes.

3. Retrieve logs from Data Grid pods as required.

   oc logs -f $POD_NAME

Procedure

1. Configure Data Grid logging with the spec.logging.categories field in your Infinispan CR.

   spec:
     logging:
       categories:
         org.infinispan: debug
         org.jgroups: debug

2. Apply the changes.

3. Retrieve logs from Data Grid pods as required.

   oc logs -f $POD_NAME

Procedure

1. Open your Infinispan CR for editing.

2. Attach labels and annotations to Data Grid resources in the metadata.annotations section.

   • Define values for annotations directly in the metadata.annotations section.
   • Define values for labels with the metadata.labels field.
3. Apply your Infinispan CR.

Procedure

1. Create a subscription definition YAML for your Data Grid Operator:

   1. Use the spec.config.env field to define environment variables.

   2. Within the ADDITIONAL_VARS variable, include environment variable names in a JSON array.

      subscription-datagrid.yaml

      apiVersion: operators.coreos.com/v1alpha1
      kind: Subscription
      metadata:
        name: datagrid
        namespace: openshift-operators
      spec:
        channel: 8.5.x
        installPlanApproval: Automatic
        name: datagrid
        source: redhat-operators
        sourceNamespace: openshift-marketplace
        config:
          env:
          - name: ADDITIONAL_VARS
            value: "[\"VAR_NAME\", \"ANOTHER_VAR\"]"
          - name: VAR_NAME
            value: $(VAR_NAME_VALUE)
          - name: ANOTHER_VAR
            value: $(ANOTHER_VAR_VALUE)

      For example, use the environment variables to set the local time zone:

      subscription-datagrid.yaml

      kind: Subscription
      spec:
        ...
        config:
          env:
          - name: ADDITIONAL_VARS
            value: "[\"TZ\"]"
          - name: TZ
            value: "JST-9"

2. Create a subscription for Data Grid Operator:

   oc apply -f subscription-datagrid.yaml

Next steps

1. Use the oc edit subscription command to modify the environment variable:

   oc edit subscription datagrid -n openshift-operators

2. To ensure the changes take effect on your Data Grid clusters, you must recreate the existing clusters. Terminate the pods by deleting the StatefulSet associated with the existing Infinispan CRs.