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:
  • Solr
  • SolrOpsRequest

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:

1. At first, a user creates a Solr Custom Resource Object (CRO).

2. KubeDB Provisioner operator watches the Solr CRO.

3. When the operator finds a Solr CR, it creates required number of PetSets and related necessary stuff like secrets, services, etc.

4. Then, in order to reconfigure the TLS configuration of the Solr database the user creates a SolrOpsRequest CR with desired information.

5. KubeDB Ops-manager operator watches the SolrOpsRequest CR.

6. When it finds a SolrOpsRequest CR, it pauses the Solr object which is referred from the SolrOpsRequest. So, the KubeDB Provisioner operator doesn’t perform any operations on the Solr object during the reconfiguring TLS process.

7. Then the KubeDB Ops-manager operator will add, remove, update or rotate TLS configuration based on the Ops Request yaml.

8. 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 the SolrOpsRequest CR.

9. After the successful reconfiguring of the Solr TLS, the KubeDB Ops-manager operator resumes the Solr object so that the KubeDB 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.