Hello takumi, There's a walk-through on deployment in Kubernetes: https://apacheignite.readme.io/docs/kubernetes-deployment
You would probably want to use StatefulSets for persistence-enabled Ignite: https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/ "Manage the deployment and scaling of a set of Pods, and provide guarantees about ordering. They do so by maintaining a unique, sticky identity for each of their Pods. Like Deployments, StatefulSets manage Pods that are based on an identical container spec. However, although their specs are the same, the Pods in a StatefulSet are not interchangeable. Each Pod has a persistent identifier that it maintains across any rescheduling." And I think that Ignite instance will know what data it holds even if its IP addess change between runs. Be wary that there are a number of articles against keeping databases in Docker containers: https://www.percona.com/blog/2016/11/16/is-docker-for-your-database/ https://myopsblog.wordpress.com/2017/02/06/why-databases-is-not-for-containers/ and Ignite with Persistence is basically a database, so be warned. -- Ilya -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Persistence-on-Kubernetes-tp16396p16512.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
