mirror of
https://github.com/helm/charts.git
synced 2026-08-21 05:17:23 +00:00
* add apache ignite helm chart Signed-off-by: Oleksii Asiutin <sutok85@gmail.com> * Disable Ignite persistence if volumes are disabled Signed-off-by: Mykola Rybak <mykola.rybak@gmail.com> * Expose peerClassLoadingEnabled property Signed-off-by: Mykola Rybak <mykola.rybak@gmail.com> * Expose environment variable configuration Signed-off-by: Mykola Rybak <mykola.rybak@gmail.com> * add service account to support rbac Signed-off-by: Oleksii Asiutin <sutok85@gmail.com> * add ability to disable rbac Signed-off-by: Oleksii Asiutin <sutok85@gmail.com> * change appVersion and chart version Signed-off-by: Oleksii Asiutin <sutok85@gmail.com> * move all ignite: configs to top-level Signed-off-by: Oleksii Asiutin <sutok85@gmail.com> * update app version to 2.7.0 Signed-off-by: Oleksii Asiutin <sutok85@gmail.com> * fixed cluster activation commands new ignite version (2.7.0) has different binaries path Signed-off-by: Oleksii Asiutin <sutok85@gmail.com> * change "dataStorage" config key to "persistence" Most helm charts use "persistence" config key. So we follow the same convention. Signed-off-by: Oleksii Asiutin <sutok85@gmail.com> * adapt chart configs to RBAC standards according to this link https://docs.helm.sh/chart_best_practices/#role-based-access-control Signed-off-by: Oleksii Asiutin <sutok85@gmail.com>
apache-ignite
This is a helm chart for Apache Ignite
Apache Ignite is an open-source distributed database, caching and processing platform designed to store and compute on large volumes of data across a cluster of nodes.
Install
$ helm install --name my-release stable/ignite
Configuring persistence
Data persistence and WAL persistence can be enabled by specifying appropriate variables. Please note that default persistence configuration is for AWS EBS.
helm install --name my-release \
--set persistence.enabled=true \
--set persistence.size=100Gi \
--set wal_persistence.enabled=true \
--set wal_persistence.size=8Gi \
stable/ignite
To configure persistence for other volume plugins you should edit
persistence.provisioner and persistence.provisioner_parameters variables.
(and the same variables for wal_persistence section).