Apache Ignite on your Kubernetes Cluster Part 3: Configuration explained
Previously we had a look on the RBAC needed for and ignite cluster in Kubernetes.
This blogs focuses on the deployment and the configuration of the cache.
The default ignite installation uses and xml based configuration. It is easy to mount files using configmaps.
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 | > kubectl get configmap ignite-cache-configmap -o yaml NAME DATA AGE ignite-cache-configmap 1 32d gkatzioura@MacBook-Pro-2 templates % kubectl get configmap ignite-cache-configmap -o yaml apiVersion: v1 data: ignite-config.xml: "....\n" kind: ConfigMap metadata: creationTimestamp: 2020-03-07T22:23:50Z name: ignite-cache-configmap namespace: default resourceVersion: "137521" selfLink: /api/v1/namespaces/default/configmaps/ignite-cache-configmap uid: ff530e3d-10d6-4708-817f-f9845886c1b0 |
Since viewing the xml from the configmap is cumbersome this is the actual xml
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 | <? xml version = "1.0" encoding = "UTF-8" ?> http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd"> < bean class = "org.apache.ignite.configuration.IgniteConfiguration" > < property name = "peerClassLoadingEnabled" value = "false" /> < property name = "dataStorageConfiguration" > < bean class = "org.apache.ignite.configuration.DataStorageConfiguration" > </ bean > </ property > < property name = "discoverySpi" > < bean class = "org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi" > < property name = "ipFinder" > < bean class = "org.apache.ignite.spi.discovery.tcp.ipfinder.kubernetes.TcpDiscoveryKubernetesIpFinder" > < property name = "namespace" value = "default" /> < property name = "serviceName" value = "ignite-cache" /> </ bean > </ property > </ bean > </ property > </ bean > </ beans > |
The default DataStorageConfiguration is being used.
What you can see different from other ignite installations is TCP discovery. The tcp discover used is using the Kubernetes TCP based discovery.
The next blog focuses on the services and the deployment.
Published on Java Code Geeks with permission by Emmanouil Gkatziouras, partner at our JCG program. See the original article here: Apache Ignite on your Kubernetes Cluster Part 3: Configuration explained Opinions expressed by Java Code Geeks contributors are their own. |