New to KubeDB? Please start here.
Reconfiguring TLS of PerconaXtraDB 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 PerconaXtraDB
database.
Before You Begin
- You should be familiar with the following
KubeDB
concepts:
How Reconfiguring PerconaXtraDB TLS Configuration Process Works
The following diagram shows how KubeDB Ops Manager reconfigures TLS of a PerconaXtraDB
database. Open the image in a new tab to see the enlarged version.
The Reconfiguring PerconaXtraDB TLS process consists of the following steps:
At first, a user creates a
PerconaXtraDB
Custom Resource Object (CRO).KubeDB
Community operator watches thePerconaXtraDB
CRO.When the operator finds a
PerconaXtraDB
CR, it creates required number ofPetSets
and related necessary stuff like secrets, services, etc.Then, in order to reconfigure the TLS configuration of the
PerconaXtraDB
database the user creates aPerconaXtraDBOpsRequest
CR with desired information.KubeDB
Enterprise operator watches thePerconaXtraDBOpsRequest
CR.When it finds a
PerconaXtraDBOpsRequest
CR, it pauses thePerconaXtraDB
object which is referred from thePerconaXtraDBOpsRequest
. So, theKubeDB
Community operator doesn’t perform any operations on thePerconaXtraDB
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 thePerconaXtraDBOpsRequest
CR.After the successful reconfiguring of the
PerconaXtraDB
TLS, theKubeDB
Enterprise operator resumes thePerconaXtraDB
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 PerconaXtraDB database using PerconaXtraDBOpsRequest
CRD.