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