Data Grid Operator Guide

Procedure

1. Extract the .zip archive for the native Data Grid CLI distribution.

2. Copy the native executable, or create a hard link, to a file named "kubectl-infinispan", for example:

   cp redhat-datagrid-cli kubectl-infinispan

   Copy to Clipboard Toggle word wrap
3. Add kubectl-infinispan to your PATH.

4. Verify that the CLI is installed.

   oc plugin list
   
   The following compatible plugins are available:
   /path/to/kubectl-infinispan

   Copy to Clipboard Toggle word wrap

5. Use the infinispan --help command to view available commands.

   oc infinispan --help

   Copy to Clipboard Toggle word wrap

Procedure

1. Log in to the OpenShift Web Console.
2. Navigate to OperatorHub.
3. Find and select Data Grid Operator.
4. Select Install and continue to Create Operator Subscription.

5. Specify options for your subscription.

   Installation Mode

   You can install Data Grid Operator into a Specific namespace or All namespaces.

   Update Channel

   Get updates for Data Grid Operator 8.4.x.

   Approval Strategies

   Automatically install updates from the 8.4.x channel or require approval before installation.

6. Select Subscribe to install Data Grid Operator.
7. Navigate to Installed Operators to verify the Data Grid Operator installation.

Procedure

1. Run the oc infinispan install command to create Data Grid Operator subscriptions, for example:

   oc infinispan install --channel=8.4.x
                              --source=redhat-operators
                              --source-namespace=openshift-marketplace

   Copy to Clipboard Toggle word wrap

2. Verify the installation.

   oc get pods -n openshift-operators | grep infinispan-operator
   NAME                                   READY   STATUS
   infinispan-operator-<id>               1/1     Running

   Copy to Clipboard Toggle word wrap

Procedure

1. Set up projects.

   1. Create a project for Data Grid Operator.

   2. If you want Data Grid Operator to control a specific Data Grid cluster only, create a project for that cluster.

      oc new-project ${INSTALL_NAMESPACE} 

      1

      
      oc new-project ${WATCH_NAMESPACE} 

      2

      Copy to Clipboard Toggle word wrap

      1

      Creates a project into which you install Data Grid Operator.

      2

      Optionally creates a project for a specific Data Grid cluster if you do not want Data Grid Operator to watch all projects.

2. Create an OperatorGroup resource.

   Control all Data Grid clusters

   oc apply -f - << EOF
   apiVersion: operators.coreos.com/v1
   kind: OperatorGroup
   metadata:
    name: datagrid
    namespace: ${INSTALL_NAMESPACE}
   EOF

   Copy to Clipboard Toggle word wrap

   Control a specific Data Grid cluster

   oc apply -f - << EOF
   apiVersion: operators.coreos.com/v1
   kind: OperatorGroup
   metadata:
    name: datagrid
    namespace: ${INSTALL_NAMESPACE}
   spec:
    targetNamespaces:
    - ${WATCH_NAMESPACE}
   EOF

   Copy to Clipboard Toggle word wrap

3. Create a subscription for Data Grid Operator.

   oc apply -f - << EOF
   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
    name: datagrid-operator
    namespace: ${INSTALL_NAMESPACE}
   spec:
    channel: 8.4.x
    installPlanApproval: Automatic
    name: datagrid
    source: redhat-operators
    sourceNamespace: openshift-marketplace
   EOF

   Copy to Clipboard Toggle word wrap
   Note

   If you want to manually approve updates from the 8.4.x channel, change the value of the spec.installPlanApproval field to Manual.

4. Verify the installation.

   oc get pods -n ${INSTALL_NAMESPACE}
   NAME                                   READY   STATUS
   infinispan-operator-<id>               1/1     Running

   Copy to Clipboard Toggle word wrap

Procedure

1. Run the infinispan create cluster command.

   For example, create a Data Grid cluster with two pods as follows:

   oc infinispan create cluster --replicas=3 -Pservice.type=DataGrid infinispan

   Copy to Clipboard Toggle word wrap
   Tip

   Add the --version argument to control the Data Grid version of your cluster. For example, --version=8.4.6-1. If you don’t specify the version, Data Grid Operator creates cluster with the latest supported Data Grid version.

2. Watch Data Grid Operator create the Data Grid pods.

   oc get pods -w

   Copy to Clipboard Toggle word wrap

Procedure

1. Create a YAML file that defines your Infinispan CR.

   For example, create a my_infinispan.yaml file that changes the number of Data Grid pods to two:

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

   Copy to Clipboard Toggle word wrap

2. Apply your Infinispan CR.

   oc apply -f my_infinispan.yaml

   Copy to Clipboard Toggle word wrap

3. Watch Data Grid Operator scale the Data Grid pods.

   oc get pods -w

   Copy to Clipboard Toggle word wrap

Procedure

1. Change the spec.replicas field to 0 to stop the Data Grid cluster.

   spec:
     replicas: 0

   Copy to Clipboard Toggle word wrap

2. Ensure you have the correct number of pods before you restart the cluster.

   oc get infinispan infinispan -o=jsonpath='{.status.replicasWantedAtRestart}'

   Copy to Clipboard Toggle word wrap

3. Change the spec.replicas field to the same number of pods to restart the Data Grid cluster.

   spec:
     replicas: 6

   Copy to Clipboard Toggle word wrap

Procedure

1. Add Data Grid configuration to a infinispan-config.[xml|yaml|json] key in the data field of your ConfigMap.

   XML

   apiVersion: v1
   kind: ConfigMap
   metadata:
      name: cluster-config
      namespace: rhdg-namespace
   data:
      infinispan-config.xml: >
        <infinispan>
          <!-- Custom configuration goes here. -->
        </infinispan>

   Copy to Clipboard Toggle word wrap

   YAML

   apiVersion: v1
   kind: ConfigMap
   metadata:
      name: cluster-config
      namespace: rhdg-namespace
   data:
      infinispan-config.yaml: >
        infinispan:
          # Custom configuration goes here.

   Copy to Clipboard Toggle word wrap

   JSON

   apiVersion: v1
   kind: ConfigMap
   metadata:
      name: cluster-config
      namespace: rhdg-namespace
   data:
      infinispan-config.json: >
        {
          "infinispan": {
          }
        }

   Copy to Clipboard Toggle word wrap

2. Create the ConfigMap from your YAML file.

   oc apply -f cluster-config.yaml

   Copy to Clipboard Toggle word wrap

3. Specify the name of the ConfigMap with the spec.configMapName field in your Infinispan CR and then apply the changes.

   spec:
     configMapName: "cluster-config"

   Copy to Clipboard Toggle word wrap

Procedure

1. Create a CredentialStore Secret file.

2. Use the data field to specify the credentials and its aliases.

   user-secret.yaml

   apiVersion: v1
   kind: Secret
   metadata:
     name: user-secret
   type: Opaque
   data:
     postgres_cred: sensitive-value
     mysql_cred: sensitive-value2

   Copy to Clipboard Toggle word wrap

3. Apply your Secret file.

   oc apply -f user-secret.yaml

   Copy to Clipboard Toggle word wrap
4. Open the Infinispan CR for editing.

5. In the spec.security.credentialStoreSecretName field, specify the name of the credential store secret.

   Infinispan CR

   spec:
     security:
       credentialStoreSecretName: user-secret

   Copy to Clipboard Toggle word wrap

6. Apply the changes.
7. Open your Data Grid Server configuration for editing.

8. Add a credential-reference to your configuration.

   1. Specify the credentials as the name of the store.

   2. Specify the alias attribute as one of the keys defined in your credential secret.

      Data Grid.xml

      <credential-store>
          <credential-reference store="credentials"  alias="postgres_cred"/>
      </credential-store>

      Copy to Clipboard Toggle word wrap

1. Gracefully shuts down the existing cluster.
2. Removes the existing cluster.
3. Creates a new cluster with the target version.

1. Creates a new Data Grid cluster with the target version that runs alongside your existing cluster.
2. Creates a remote cache store to transfer data from the existing cluster to the new cluster.
3. Redirects all clients to the new cluster.
4. Removes the existing cluster when all data and client connections are transferred to the new cluster.

Procedure

1. Specify the Data Grid version number in the spec.version field.

2. Ensure that Shutdown is set as the value for the spec.upgrades.type field, which is the default.

   spec:
     version: 8.4.6-1
     upgrades:
       type: Shutdown

   Copy to Clipboard Toggle word wrap
3. Apply your changes, if necessary.

Procedure

1. Specify the Data Grid version number in the spec.version field.

2. Specify HotRodRolling as the value for the spec.upgrades.type field.

   spec:
     version: 8.4.6-1
     upgrades:
       type: HotRodRolling

   Copy to Clipboard Toggle word wrap
3. Apply your changes.

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

   Copy to Clipboard Toggle word wrap
   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

   Copy to Clipboard Toggle word wrap
   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."

   Copy to Clipboard Toggle word wrap

2. Create the priority class.

   oc create -f high-priority.yaml

   Copy to Clipboard Toggle word wrap

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

   Infinispan CR

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

   Copy to Clipboard Toggle word wrap

   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.categories field in your Infinispan CR.

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

   Copy to Clipboard Toggle word wrap
2. Apply the changes.

3. Retrieve logs from Data Grid pods as required.

   oc logs -f $POD_NAME

   Copy to Clipboard Toggle word wrap

Procedure

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

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

   Copy to Clipboard Toggle word wrap
2. Apply your Infinispan CR to create the cluster.

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.4.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)

      Copy to Clipboard Toggle word wrap

      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"

      Copy to Clipboard Toggle word wrap

2. Create a subscription for Data Grid Operator:

   oc apply -f subscription-datagrid.yaml

   Copy to Clipboard Toggle word wrap

Next steps

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

   oc edit subscription datagrid -n openshift-operators

   Copy to Clipboard Toggle word wrap
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.

Procedure

1. Create an identities.yaml file with the credentials that you want to add.

   credentials:
   - username: myfirstusername
     password: changeme-one
   - username: mysecondusername
     password: changeme-two

   Copy to Clipboard Toggle word wrap

2. Create an authentication secret from identities.yaml.

   oc create secret generic --from-file=identities.yaml connect-secret

   Copy to Clipboard Toggle word wrap

3. Specify the authentication secret with spec.security.endpointSecretName in your Infinispan CR and then apply the changes.

   spec:
     security:
       endpointSecretName: connect-secret

   Copy to Clipboard Toggle word wrap

Procedure

1. Set false as the value for the spec.security.endpointAuthentication field in your Infinispan CR.

   spec:
     security:
       endpointAuthentication: false

   Copy to Clipboard Toggle word wrap
2. Apply the changes.

Procedure

1. Set either Validate or Authenticate as the value for the spec.security.endpointEncryption.clientCert field in your Infinispan CR.

   Note

   The default value is None.

2. Specify the secret that contains the client trust store with the spec.security.endpointEncryption.clientCertSecretName field.

   By default Data Grid Operator expects a trust store secret named <cluster-name>-client-cert-secret.

   Note

   The secret must be unique to each Infinispan CR instance in the OpenShift cluster. When you delete the Infinispan CR, OpenShift also automatically deletes the associated secret.

   spec:
     security:
       endpointEncryption:
           type: Secret
           certSecretName: tls-secret
           clientCert: Validate
           clientCertSecretName: infinispan-client-cert-secret

   Copy to Clipboard Toggle word wrap
3. Apply the changes.

Procedure

1. Specify the name of the secret that contains the client trust store as the value of the metadata.name field.

   Note

   The name must match the value of the spec.security.endpointEncryption.clientCertSecretName field.

2. Provide the password for the trust store with the stringData.truststore-password field.

3. Specify the trust store with the data.truststore.p12 field.

   apiVersion: v1
   kind: Secret
   metadata:
     name: infinispan-client-cert-secret
   type: Opaque
   stringData:
       truststore-password: changme
   data:
       truststore.p12:  "<base64_encoded_PKCS12_trust_store>"

   Copy to Clipboard Toggle word wrap
4. Apply the changes.

Procedure

1. Specify the name of the secret that contains the client trust store as the value of the metadata.name field.

   Note

   The name must match the value of the spec.security.endpointEncryption.clientCertSecretName field.

2. Specify the signing certificate, or CA certificate bundle, as the value of the data.trust.ca field.

3. If you use the Authenticate strategy to verify client identities, add the certificate for each client that can connect to Data Grid endpoints with the data.trust.cert.<name> field.

   Note

   Data Grid Operator uses the <name> value as the alias for the certificate when it generates the trust store.

4. Optionally provide a password for the trust store with the stringData.truststore-password field.

   If you do not provide one, Data Grid Operator sets "password" as the trust store password.

   apiVersion: v1
   kind: Secret
   metadata:
     name: infinispan-client-cert-secret
   type: Opaque
   stringData:
       truststore-password: changme
   data:
       trust.ca: "<base64_encoded_CA_certificate>"
       trust.cert.client1: "<base64_encoded_client_certificate>"
       trust.cert.client2: "<base64_encoded_client_certificate>"

   Copy to Clipboard Toggle word wrap
5. Apply the changes.

Procedure

1. Set None as the value for the spec.security.endpointEncryption.type field in your Infinispan CR.

   spec:
     security:
       endpointEncryption:
         type: None

   Copy to Clipboard Toggle word wrap
2. Apply the changes.

Procedure

1. Add the encryption secret to your OpenShift namespace, for example:

   oc apply -f tls_secret.yaml

   Copy to Clipboard Toggle word wrap

2. Specify the encryption secret with the spec.security.endpointEncryption.certSecretName field in your Infinispan CR.

   spec:
     security:
       endpointEncryption:
         type: Secret
         certSecretName: tls-secret

   Copy to Clipboard Toggle word wrap
3. Apply the changes.

Procedure

1. Set true as the value for the spec.security.authorization.enabled field in your Infinispan CR.

   spec:
     security:
       authorization:
         enabled: true

   Copy to Clipboard Toggle word wrap
2. Apply the changes.

Procedure

1. Create an identities.yaml file that assigns roles to users.

   credentials:
     - username: admin
       password: changeme
     - username: my-user-1
       password: changeme
       roles:
         - admin
     - username: my-user-2
       password: changeme
       roles:
         - monitor

   Copy to Clipboard Toggle word wrap

2. Create an authentication secret from identities.yaml.

   If necessary, delete the existing secret first.

   oc delete secret connect-secret --ignore-not-found
   oc create secret generic --from-file=identities.yaml connect-secret

   Copy to Clipboard Toggle word wrap

3. Specify the authentication secret with spec.security.endpointSecretName in your Infinispan CR and then apply the changes.

   spec:
     security:
       endpointSecretName: connect-secret

   Copy to Clipboard Toggle word wrap

Procedure

1. Open your Infinispan CR for editing.

2. Specify custom roles and their associated permissions with the spec.security.authorization.roles field.

   spec:
     security:
       authorization:
         enabled: true
         roles:
           - name: my-role-1
             permissions:
               - ALL
           - name: my-role-2
             permissions:
               - READ
               - WRITE

   Copy to Clipboard Toggle word wrap
3. Apply the changes.

Procedure

1. Include spec.expose in your Infinispan CR.
2. Specify LoadBalancer as the service type with the spec.expose.type field.

3. Optionally specify the network port where the service is exposed with the spec.expose.port field.

   spec:
     expose:
       type: LoadBalancer
       port: 65535

   Copy to Clipboard Toggle word wrap
4. Apply the changes.

5. Verify that the -external service is available.

   oc get services | grep external

   Copy to Clipboard Toggle word wrap

Procedure

1. Include spec.expose in your Infinispan CR.
2. Specify NodePort as the service type with the spec.expose.type field.

3. Configure the port where Data Grid is exposed with the spec.expose.nodePort field.

   spec:
     expose:
       type: NodePort
       nodePort: 30000

   Copy to Clipboard Toggle word wrap
4. Apply the changes.

5. Verify that the -external service is available.

   oc get services | grep external

   Copy to Clipboard Toggle word wrap

Procedure

1. Include spec.expose in your Infinispan CR.
2. Specify Route as the service type with the spec.expose.type field.

3. Optionally add a hostname with the spec.expose.host field.

   spec:
     expose:
       type: Route
       host: www.example.org

   Copy to Clipboard Toggle word wrap
4. Apply the changes.

5. Verify that the route is available.

   oc get routes

   Copy to Clipboard Toggle word wrap

Procedure

1. Create an Infinispan CR for each Data Grid cluster.
2. Specify the name of the local site with spec.service.sites.local.name.

3. Configure the expose type for cross-site replication.

   1. Set the value of the spec.service.sites.local.expose.type field to one of the following:

      • NodePort
      • LoadBalancer
      • Route

   2. Optionally specify a port or custom hostname with the following fields:

      • spec.service.sites.local.expose.nodePort if you use a NodePort service.
      • spec.service.sites.local.expose.port if you use a LoadBalancer service.
      • spec.service.sites.local.expose.routeHostName if you use an OpenShift Route.

4. Provide the name and static URL for each Data Grid cluster that acts as a backup location with spec.service.sites.locations, for example:

   • LON

     apiVersion: infinispan.org/v1
     kind: Infinispan
     metadata:
       name: infinispan
     spec:
       replicas: 3
       version: <Data Grid_version>
       service:
         type: DataGrid
         sites:
           local:
             name: LON
             expose:
               type: LoadBalancer
               port: 65535
             maxRelayNodes: 1
           locations:
             - name: NYC
               url: infinispan+xsite://infinispan-nyc.myhost.com:7900
       logging:
         categories:
           org.jgroups.protocols.TCP: error
           org.jgroups.protocols.relay.RELAY2: error

     Copy to Clipboard Toggle word wrap

   • NYC

     apiVersion: infinispan.org/v1
     kind: Infinispan
     metadata:
       name: infinispan
     spec:
       replicas: 2
       version: <Data Grid_version>
       service:
         type: DataGrid
         sites:
           local:
             name: NYC
             expose:
               type: LoadBalancer
               port: 65535
             maxRelayNodes: 1
           locations:
             - name: LON
               url: infinispan+xsite://infinispan-lon.myhost.com
       logging:
         categories:
           org.jgroups.protocols.TCP: error
           org.jgroups.protocols.relay.RELAY2: error

     Copy to Clipboard Toggle word wrap
     Important

     Be sure to adjust logging categories in your Infinispan CR to decrease log levels for JGroups TCP and RELAY2 protocols. This prevents a large number of log files from uses container storage.

     spec:
       logging:
         categories:
           org.jgroups.protocols.TCP: error
           org.jgroups.protocols.relay.RELAY2: error

     Copy to Clipboard Toggle word wrap
5. Configure your Infinispan CRs with any other Data Grid service resources and then apply the changes.

6. Verify that Data Grid clusters form a cross-site view.

   1. Retrieve the Infinispan CR.

      oc get infinispan -o yaml

      Copy to Clipboard Toggle word wrap
   2. Check for the type: CrossSiteViewFormed condition.

Procedure

1. Allocate the number of CPU units using the service.sites.local.discovery.cpu field.

2. Allocate the amount of memory, in bytes, using the service.sites.local.discovery.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.

Procedure

1. Create an Infinispan CR for each Data Grid cluster.
2. Specify the name of the local site with the spec.service.sites.local.name field.
3. For the LON cluster, set false as the value for the spec.service.sites.local.discovery.launchGossipRouter field.
4. For the LON cluster, specify the url with the spec.service.sites.locations.url to connect to the NYC.

5. In the NYC configuration, do not specify the spec.service.sites.locations.url.

   LON

   apiVersion: infinispan.org/v1
   kind: Infinispan
   metadata:
     name: infinispan
   spec:
     replicas: 3
     service:
       type: DataGrid
       sites:
         local:
           name: LON
           discovery:
             launchGossipRouter: false
         locations:
           - name: NYC
             url: infinispan+xsite://infinispan-nyc.myhost.com:7900

   Copy to Clipboard Toggle word wrap

   NYC

   apiVersion: infinispan.org/v1
   kind: Infinispan
   metadata:
     name: infinispan
   spec:
     replicas: 3
     service:
       type: DataGrid
       sites:
         local:
           name: NYC
         locations:
           - name: LON

   Copy to Clipboard Toggle word wrap