New to KubeDB? Please start here.
Reconfiguring TLS of SingleStore Database
This guide will give an overview on how KubeDB Ops Manager reconfigures TLS configuration i.e. add TLS, remove TLS, update issuer/cluster issuer or Certificates and rotate the certificates of a SingleStore
database.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How Reconfiguring SingleStore TLS Configuration Process Works
The following diagram shows how KubeDB Ops Manager reconfigures TLS of a SingleStore
database. Open the image in a new tab to see the enlarged version.
The Reconfiguring SingleStore TLS process consists of the following steps:
At first, a user creates a
SingleStore
Custom Resource Object (CRO).KubeDB
Provisioner operator watches theSingleStore
CRO.When the operator finds a
SingleStore
CR, it creates required number ofPetSets
and related necessary stuff like secrets, services, etc.Then, in order to reconfigure the TLS configuration of the
SingleStore
database the user creates aSingleStoreOpsRequest
CR with desired information.KubeDB
Ops-manager operator watches theSingleStoreOpsRequest
CR.When it finds a
SingleStoreOpsRequest
CR, it pauses theSingleStore
object which is referred from theSingleStoreOpsRequest
. So, theKubeDB
Community operator doesn’t perform any operations on theSingleStore
object during the reconfiguring TLS process.Then the
KubeDB
Enterprise operator will add, remove, update or rotate TLS configuration based on the Ops Request yaml.Then the
KubeDB
Enterprise operator will restart all the Pods of the database so that they restart with the new TLS configuration defined in theSingleStoreOpsRequest
CR.After the successful reconfiguring of the
SingleStore
TLS, theKubeDB
Enterprise operator resumes theSingleStore
object so that theKubeDB
Community 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 SingleStore database using SingleStoreOpsRequest
CRD.