Answer the question
In order to leave comments, you need to log in
How to deploy Apache Ignite in Kubernetes cluster using local config?
There is a Kubernetes cluster without additional settings, but with an unrouted network of pods. Local network 10.100.0.0/16, service network 10.100.200.0/24, pod network 10.200.0.0/16. I'm trying to deploy Apache Ignite into it according to the manual from the developers https://apacheignite.readme.io/docs/stateful-deployment, ran into a problem: at startup, it tries to download the config from github, naturally breaks off and does not want to work further. The CONFIG_URI parameter inside statefulset.yaml is responsible for determining the location, which was copied one to one from the training manual. The docs indicate that this parameter can be stuffed not only with the URI as such, but also with the local or absolute path to the config. That's just the config itself is not naturally put inside the docker image, and the Internet is not available from the pod (nefig!). Question: how can I properly shove the config into the kubernetes statefulset so that the kuber takes it into itself and puts ignit in access?
Answer the question
In order to leave comments, you need to log in
1. Use file path in CONFIG_URI: file:///...
2. Load config into ConfigMap or Secret
3. Modify statefulset manifest by adding volume based on cm/secret with config file.
Optionally, use a stable chart: https://github.com/helm/charts/tree/master/stable/...
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question