This JSON Schema defines the configuration for cassandra DB instance.
Property | Type | Required | Description |
---|---|---|---|
cassandra_version |
string | Yes | Version of Cassandra e.g. 3.11.6 |
size |
object | Yes | Sizing attribute for cassandra instance |
The size details
Property | Type | Required | Description |
---|---|---|---|
replica_count |
integer | Yes | Number of cassandra instances needs to be deployed [DEPRECATED] |
instance_count |
integer | Yes | Number of cassandra instances needs to be deployed |
cpu |
string | No | CPU request in format mentioned @ https://kubernetes.io/docs/concepts/configuration/manage-resources-containers |
memory |
string | No | Memory request in format mentioned @ https://kubernetes.io/docs/concepts/configuration/manage-resources-containers |
volume |
string | No | Volume request in kubernetes persistent volumes |
Additional fields if any for a particular implementation of a resource
Property | Type | Required | Description |
---|---|---|---|
k8s |
object | No | Advanced k8s values for cassandra |
Advanced k8s values for mongo
Property | Type | Required | Description |
---|---|---|---|
cassandra |
object | No | Advanced values for cassandra |
Advanced values for cassandra
Property | Type | Required | Description |
---|---|---|---|
values |
object | No | Helm values as per the Bitnami cassandra chart |
Property | Type | Required | Description |
---|---|---|---|
interfaces |
object | Yes | Connection details of type Cassandra DB |
It is important to find a balance between the resource requests, limits and heap size in order for cassandra pod to start.
for Eg:
limits:
cpu: 2
memory: 3Gi
requests:
cpu: 2
memory: 2Gi
maxHeapSize: 2G
newHeapSize: 1G