Chapter 5. Configuring Data Grid clusters
Chapter 5. Configuring Data Grid clusters Apply custom Data Grid configuration to clusters that Data Grid Operator manages. 5.1. Applying custom configuration to Data Grid clusters Add Data Grid configuration to a ConfigMap and make it available to Data Grid Operator. Data Grid Operator can then apply the custom configuration to your Data Grid cluster. Important Data Grid Operator applies default configuration on top of your custom configuration to ensure it can continue to manage your Data Grid clusters. Be careful when applying custom configuration outside the cache-container element or field. You can apply custom configuration to underlying Data Grid Server mechanisms such as endpoints, security realms, and cluster transport. Changing this configuration can result in error and result in service downtime for your Data Grid deployment. Tip Use the Data Grid Helm chart to deploy clusters of fully configurable Data Grid Server instances on OpenShift. Prerequisites Have valid Data Grid configuration in XML, YAML, or JSON format. Procedure Add Data Grid configuration to a infinispan-config.[xml|yaml|json] key in the data field of your ConfigMap . XML YAML JSON Create the ConfigMap from your YAML file. Specify the name of the ConfigMap with the spec.configMapName field in your Infinispan CR and then apply the changes. steps If your cluster is already running Data Grid Operator restarts it to apply the configuration. Each time you modify the Data Grid configuration in the ConfigMap , Data Grid Operator detects the updates and restarts the cluster to apply the changes. Additional resources Data Grid Helm chart 5.2. Custom Data Grid configuration You can add Data Grid configuration to a ConfigMap in XML, YAML, or JSON format. 5.2.1. Cache template XML <infinispan> <cache-container> <distributed-cache-configuration name="base-template"> <expiration lifespan="5000"/> </distributed-cache-configuration> <distributed-cache-configuration name="extended-template" configuration="base-template"> <encoding media-type="application/x-protostream"/> <expiration lifespan="10000" max-idle="1000"/> </distributed-cache-configuration> </cache-container> </infinispan> YAML infinispan: cacheContainer: caches: base-template: distributedCacheConfiguration: expiration: lifespan: "5000" extended-template: distributedCacheConfiguration: configuration: "base-template" encoding: mediaType: "application/x-protostream" expiration: lifespan: "10000" maxIdle: "1000" JSON { "infinispan" : { "cache-container" : { "caches" : { "base-template" : { "distributed-cache-configuration" : { "expiration" : { "lifespan" : "5000" } } }, "extended-template" : { "distributed-cache-configuration" : { "configuration" : "base-template", "encoding": { "media-type": "application/x-protostream" }, "expiration" : { "lifespan" : "10000", "max-idle" : "1000" } } } } } } } 5.2.2. Logging configuration You can also include Apache Log4j configuration in XML format as part of your ConfigMap . Note Use the spec.logging.categories field in your Infinispan CR to adjust logging levels for Data Grid clusters. Add Apache Log4j configuration only if you require advanced file-based logging capabilities. Additional resources Custom Data Grid configuration 5.3. Securing custom Data Grid configuration Securely define and store custom Data Grid Server configuration. To protect sensitive text strings such as passwords, add the entries in a credential store rather than directly in the Data Grid Server configuration. Prerequisites Have a valid Data Grid configuration in XML, YAML, or JSON format. Procedure Create a CredentialStore Secret file. 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 Apply your Secret file. Open the Infinispan CR for editing. In the spec.security.credentialStoreSecretName field, specify the name of the credential store secret. Infinispan CR spec: security: credentialStoreSecretName: user-secret Apply the changes. Open your Data Grid Server configuration for editing. Add a credential-reference to your configuration. Specify the credentials as the name of the store . Specify the alias attribute as one of the keys defined in your credential secret. Data Grid.xml Additional resources Credential store references
apiVersion: v1 kind: ConfigMap metadata: name: cluster-config namespace: rhdg-namespace data: infinispan-config.xml: > <infinispan> <!-- Custom configuration goes here. --> </infinispan> apiVersion: v1 kind: ConfigMap metadata: name: cluster-config namespace: rhdg-namespace data: infinispan-config.yaml: > infinispan: # Custom configuration goes here. apiVersion: v1 kind: ConfigMap metadata: name: cluster-config namespace: rhdg-namespace data: infinispan-config.json: > { "infinispan": { } } apply -f cluster-config.yaml spec: configMapName: "cluster-config" <infinispan> <cache-container> <distributed-cache-configuration name="base-template"> <expiration lifespan="5000"/> </distributed-cache-configuration> <distributed-cache-configuration name="extended-template" configuration="base-template"> <encoding media-type="application/x-protostream"/> <expiration lifespan="10000" max-idle="1000"/> </distributed-cache-configuration> </cache-container> </infinispan> infinispan: cacheContainer: caches: base-template: distributedCacheConfiguration: expiration: lifespan: "5000" extended-template: distributedCacheConfiguration: configuration: "base-template" encoding: mediaType: "application/x-protostream" expiration: lifespan: "10000" maxIdle: "1000" { "infinispan" : { "cache-container" : { "caches" : { "base-template" : { "distributed-cache-configuration" : { "expiration" : { "lifespan" : "5000" } } }, "extended-template" : { "distributed-cache-configuration" : { "configuration" : "base-template", "encoding": { "media-type": "application/x-protostream" }, "expiration" : { "lifespan" : "10000", "max-idle" : "1000" } } } } } } } apiVersion: v1 kind: ConfigMap metadata: name: logging-config namespace: rhdg-namespace data: infinispan-config.xml: > <infinispan> <!-- Add custom Data Grid configuration if required. --> <!-- You can provide either Data Grid configuration, logging configuration, or both. --> </infinispan> log4j.xml: > <?xml version="1.0" encoding="UTF-8"?> <Configuration name="ServerConfig" monitorInterval="60" shutdownHook="disable"> <Appenders> <!-- Colored output on the console --> <Console name="STDOUT"> <PatternLayout pattern="%d{HH:mm:ss,SSS} %-5p (%t) [%c] %m%throwable%n"/> </Console> </Appenders> <Loggers> <Root level="INFO"> <AppenderRef ref="STDOUT" level="TRACE"/> </Root> <Logger name="org.infinispan" level="TRACE"/> </Loggers> </Configuration> apiVersion: v1 kind: Secret metadata: name: user-secret type: Opaque data: postgres_cred: sensitive-value mysql_cred: sensitive-value2 apply -f user-secret.yaml spec: security: credentialStoreSecretName: user-secret <credential-store> <credential-reference store="credentials" alias="postgres_cred"/> </credential-store>