K8ssandra release notes
K8ssandra provides a production-ready platform for running Apache Cassandra® on Kubernetes. This includes automation for operational tasks such as repairs, backup and restores, and monitoring.
Also deployed is Stargate, an open source data gateway that lets you interact programmatically with your Kubernetes-hosted Cassandra resources via a well-defined API.
NoteThe K8ssandra 1.1.0 release implements a number of changes, enhancements, and bug fixes. This Release Notes topic lists a subset of the key updates. For the complete list, see the CHANGELOG.
Release date: 09-April-2021.
- A Kubernetes v1.16 or later environment - local or via a supported cloud provider
- Helm v3
Supported Kubernetes environments
- Open-source kubernetes.io
- Google Kubernetes Engine (GKE)
- Microsoft Azure Kubernetes Service (AKS)
- Amazon Elastic Kubernetes Service (EKS)
K8ssandra deployed components
The K8ssandra helm chart deploys the following components. Some are optional, and depending on the configuration, may not be deployed:
- Apache Cassandra - the deployed version depends on the configured
- 3.11.10 (default)
- DataStax Kubernetes Operator for Apache Cassandra (cass-operator) 1.6.0
- Management API for Apache Cassandra (MAAC) 0.1.24
- Stargate 1.0.18
- Metric Collector for Apache Cassandra (MCAC) 0.2.0
- kube-prometheus-stack 12.11.3 chart
- Medusa for Apache Cassandra 0.10.0
- Reaper for Apache Cassandra 2.2.2
Upgrading from K8ssandra 1.0.0 to 1.1.0 causes a StatefulSet update (due to #533 and #613). A StatefulSet update has the effect of a rolling restart. Because of #411 this could require you to perform a manual restart of all Stargate nodes after the Cassandra cluster is back online. This behavior also impacts in-place restore operations of Medusa backups #611.
To manually restart Stargate nodes:
- Get the Deployment object in your Kubernetes environment:
kubectl get deployment | grep stargate
- Scale down with this command:
kubectl scale deployment <stargate-deployment> --replicas 0
- Run this next command and wait until it reports 0/0 ready replicas. This should happen within a couple seconds.
kubectl get deployment <stargate-deployment>
- Now scale up with:
kubectl scale deployment <stargate-deployment> --replicas 1
K8ssandra 1.1.0 revisions
Each of the following sections present a subset of key devlopments in K8ssandra 1.1.0. For the complete list, see the CHANGELOG.
- Shut down cluster by default with in-place restores of Medusa backups #611.
Important!The new default behavior for in-place restores, which now shut down the whole cluster by default, will require Stargate nodes to be restarted after the Cassandra cluster is back online. See the Upgrade notice above.
- Update Management API image locations #637.
- Add option to disable Cassandra logging sidecar #576.
- Developer documentation #239.
- Add support for
additionalSeedsin the CassandraDatacenter #547.
- Scale up fails if a restore was performed in the past #616.
- S3-compliant MinIO buckets for Medusa backup and restore operations, and related edits for the separate Amazon S3 topic #556. For the updates, start in Backup and restore Cassandra data.
- Migrating existing Cassandra to K8ssandra #377. See Migrating a Cassandra cluster to K8ssandra.
- Underlying considerations for scaling nodes up/down #501. See Scale your Cassandra cluster in K8ssandra.
Your feedback and contributions are welcome! To contribute, fork the K8ssandra repo and submit Pull Requests (PRs) for review.
To submit documentation comments or edits, see Contribution guidelines.
Read the K8ssandra FAQs - for starters, how to pronounce “K8ssandra.”
If you’re impatient, jump right in with the K8ssandra install steps.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.