Chapter 16. Concepts to automate Data Grid CLI commands
When interacting with an external Data Grid in Kubernetes, the Batch CR allows you to automate this using standard oc commands.
16.1. When to use it
Use this when automating interactions on Kubernetes. This avoids providing usernames and passwords and checking shell script outputs and their status.
For human interactions, the CLI shell might still be a better fit.
16.2. Example
The following Batch CR takes a site offline as described in the operational procedure Switch over to the secondary site.
apiVersion: infinispan.org/v2alpha1 kind: Batch metadata: name: take-offline namespace: keycloak 1 spec: cluster: infinispan 2 config: | 3 site take-offline --all-caches --site=site-a site status --all-caches --site=site-a
Once the CR has been created, wait for the status to show the completion.
oc -n keycloak wait --for=jsonpath='{.status.phase}'=Succeeded Batch/take-offline
Modifying a Batch CR instance has no effect. Batch operations are “one-time” events that modify Infinispan resources. To update .spec fields for the CR, or when a batch operation fails, you must create a new instance of the Batch CR.
16.3. Further reading
For more information, see the Data Grid Operator Batch CR documentation.
