New to KubeDB? Please start here.
Reconfiguring TLS of Cassandra
This guide will give an overview on how KubeDB Ops-manager operator reconfigures TLS configuration i.e. add TLS, remove TLS, update issuer/cluster issuer or Certificates and rotate the certificates of Cassandra.
Before You Begin
- You should be familiar with the following
KubeDBconcepts:
How Reconfiguring Cassandra TLS Configuration Process Works
The following diagram shows how KubeDB Ops-manager operator reconfigures TLS of a Cassandra. Open the image in a new tab to see the enlarged version.
The Reconfiguring Cassandra TLS process consists of the following steps:
At first, a user creates a
CassandraCustom Resource Object (CRO).KubeDBProvisioner operator watches theCassandraCRO.When the operator finds a
CassandraCR, it creates required number ofPetSetsand related necessary stuff like secrets, services, etc.Then, in order to reconfigure the TLS configuration of the
Cassandradatabase the user creates aCassandraOpsRequestCR with desired information.KubeDBOps-manager operator watches theCassandraOpsRequestCR.When it finds a
CassandraOpsRequestCR, it pauses theCassandraobject which is referred from theCassandraOpsRequest. So, theKubeDBProvisioner operator doesn’t perform any operations on theCassandraobject during the reconfiguring TLS process.Then the
KubeDBOps-manager operator will add, remove, update or rotate TLS configuration based on the Ops Request yaml.Then the
KubeDBOps-manager operator will restart all the Pods of the database so that they restart with the new TLS configuration defined in theCassandraOpsRequestCR.After the successful reconfiguring of the
CassandraTLS, theKubeDBOps-manager operator resumes theCassandraobject so that theKubeDBProvisioner operator resumes its usual operations.
In the next docs, we are going to show a step by step guide on reconfiguring TLS configuration of a Cassandra database using CassandraOpsRequest CRD.