cassandra-operator
cassandra-operator copied to clipboard
instaclustr
Kubernetes operator for Apache Cassandra
In order to limit the amount of [voluntary](https://kubernetes.io/docs/concepts/workloads/pods/disruptions/#voluntary-and-involuntary-disruptions) pod terminations, e.g. during Kubernetes [cluster updates](https://cloud.google.com/kubernetes-engine/docs/concepts/cluster-upgrades), we should deploy a [PodDisruptionBudget](https://kubernetes.io/docs/tasks/run-application/configure-pdb/) that limits the number of Cassandra nodes that can be...
Support for automatic repairs... likely let's just use reaper.
Ideally, we should have "core" of operator written in such way it is irrelevant what API we are using. Right now, the version of API is intrinsically tightly-coupled with the...
Upon a user modifying a configmap, we need to detect this change and gracefully propagate it throughout the cluster that references that configmap.
The current implementation of https://github.com/instaclustr/cassandra-operator/blob/1248f73f95e937010203f9eb74f7180641c550c3/pkg/controller/cassandradatacenter/configmap.go#L22 is in my opinion unnecessarily complex and could use some improvement. The way the function calls are structured makes it difficult to follow the code...
There are `icon` fields missing in `Chart.yaml` for both charts and `helm lint` says this: ``` [smiklosovic@E091-FED helm]$ helm lint cassandra ==> Linting cassandra [INFO] Chart.yaml: icon is recommended 1...
At the moment the operator produces log messages in the following format: ``` {"level":"info","ts":1566906621.2220764,"logger":"controller_cassandradatacenter","msg":"CassandraDataCenter reconciliation complete.","Request.Namespace":"default","Request.Name":"cassandra-sample-dc"} ``` It might be nicer to have human-readable timestamps.
I cannot figure out how to make a private team discussion topic visible or share it. So I'm going to move the certificate management discussion to a repo issue. From...