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