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