Files
charts/bitnami/cassandra
2018-11-12 17:29:02 +01:00
..
2018-11-12 17:28:00 +01:00
2018-11-08 16:27:11 +01:00
2018-11-12 15:50:24 +01:00
2018-11-12 13:28:53 +01:00
2018-11-12 17:28:00 +01:00

cassandra

cassandra Apache Cassandra is a free and open-source distributed database management system designed to handle large amounts of data across many commodity servers or datacenters.

TL;DR;

$ helm repo add bitnami https://charts.bitnami.com/bitnami
$ helm install bitnami/cassandra

Introduction

This chart bootstraps a Cassandra deployment on a Kubernetes cluster using the Helm package manager.

Bitnami charts can be used with Kubeapps for deployment and management of Helm Charts in clusters.

Prerequisites

  • Kubernetes 1.8+
  • PV provisioner support in the underlying infrastructure

Installing the Chart

To install the chart with the release name my-release:

$ helm install --name my-release bitnami/cassandra

The command deploys one node with Cassandra on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

Tip

: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release release:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

The following tables lists the configurable parameters of the cassandra chart and their default values.

Parameter Description Default
global.imageRegistry Global Docker Image registry nil
image.registry Cassandra Image registry docker.io
image.repository Cassandra Image name bitnami/cassandra
image.tag Cassandra Image tag {VERSION}
image.pullPolicy Image pull policy Always
image.pullSecrets Specify docker-registry secret names as an array nil
service.type Kubernetes Service type ClusterIP
service.nodePort Kubernetes Service nodePort nil
service.loadBalancerIP LoadBalancerIP if service type is LoadBalancer nil
service.annotations Annotations for the service {}
persistence.enabled Use PVCs to persist data true
persistence.storageClass Persistent Volume Storage Class generic
persistence.annotations Persistent Volume Claim annotations Annotations {}
persistence.accessModes Persistent Volume Access Modes [ReadWriteOnce]
persistence.size Persistent Volume Size 8Gi
resources CPU/Memory resource requests/limits {}
cluster.name Cassandra cluster name cassandra
cluster.replicaCount Number of Cassandra nodes 1
cluster.seedCount Number of seed nodes (note: must be greater or equal than 1 and less or equal to cluster.replicaCount) 1
cluster.numTokens Number of tokens for each node 256
cluster.datacenter Datacenter name dc1
cluster.rack Rack name rack1
cluster.enableRPC Enable Thrift RPC endpoint true
cluster.jvm.extraOpts Set the value for Java Virtual Machine extra optinos (JVM_EXTRA_OPTS) nil
cluster.jvm.maxHeapSize Set Java Virtual Machine maximum heap size (MAX_HEAP_SIZE). Calculated automatically if nil nil
cluster.jvm.newHeapSize Set Java Virtual Machine new heap size (HEAP_NEWSIZE). Calculated automatically if nil nil
dbUser.user Cassandra admin user cassandra
dbUser.forcePassword Force the user to provide a non-empty password for dbUser.user false
dbUser.password Password for dbUser.user. Randomly generated if empty (Random generated)
dbUser.existingSecret Use an existing secret object for dbUser.user password (will ignore dbUser.password) nil
startupCQL Startup CQL commands (done in the first node). Useful for creating keyspaces at startup, for instance nil
livenessProbe.enabled Turn on and off liveness probe true
livenessProbe.initialDelaySeconds Delay before liveness probe is initiated 30
livenessProbe.periodSeconds How often to perform the probe 30
livenessProbe.timeoutSeconds When the probe times out 5
livenessProbe.successThreshold Minimum consecutive successes for the probe to be considered successful after having failed 1
livenessProbe.failureThreshold Minimum consecutive failures for the probe to be considered failed after having succeeded. 5
readinessProbe.enabled Turn on and off readiness probe true
readinessProbe.initialDelaySeconds Delay before readiness probe is initiated 5
readinessProbe.periodSeconds How often to perform the probe 10
readinessProbe.timeoutSeconds When the probe times out 5
readinessProbe.successThreshold Minimum consecutive successes for the probe to be considered successful after having failed 1
readinessProbe.failureThreshold Minimum consecutive failures for the probe to be considered failed after having succeeded. 5
podAnnotations Additional pod annotations {}
podLabels Additional pod labels {}
statefulset.updateStrategy Update strategy for StatefulSet onDelete
statefulset.rollingUpdatePartition Partition update strategy nil
securityContext.enabled Enable security context true
securityContext.fsGroup Group ID for the container 1001
securityContext.runAsUser User ID for the container 1001
affinity Enable node/pod affinity {}
tolerations Toleration labels for pod assignment []
networkPolicy.enabled Enable NetworkPolicy false
networkPolicy.allowExternal Don't require client label for connections true
metrics.enabled Start a side-car prometheus exporter false
metrics.image.registry Cassandra exporter Image registry docker.io
metrics.image.repository Cassandra exporter Image name criteo/cassandra_exporter
metrics.image.tag Cassandra exporter Image tag 2.0.4
metrics.image.pullPolicy Image pull policy IfNotPresent
metrics.image.pullSecrets Specify docker-registry secret names as an array nil
metrics.podAnnotations Additional annotations for Metrics exporter {prometheus.io/scrape: "true", prometheus.io/port: "8080"}
metrics.resources Exporter resource requests/limit {}

The above parameters map to the env variables defined in bitnami/cassandra. For more information please refer to the bitnami/cassandra image documentation.

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm install --name my-release \
  --set dbUser.user=admin,dbUser.password=password\
    bitnami/cassandra

Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,

$ helm install --name my-release -f values.yaml bitnami/cassandra

Tip

: You can use the default values.yaml

Persistence

The Bitnami cassandra image stores the cassandra data at the /bitnami/cassandra path of the container.

Persistent Volume Claims are used to keep the data across deployments. This is known to work in GCE, AWS, and minikube. See the Configuration section to configure the PVC or to disable persistence.