We use cookies and other similar technology to collect data to improve your experience on our site, as described in our Privacy Policy.
Run Production-Grade Databases on Kubernetes
Backup and Recovery Solution for Kubernetes
Run Production-Grade Vault on Kubernetes
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
KubeDB simplifies Provision, Upgrade, Scaling, Volume Expansion, Monitor, Backup, Restore for various Databases in Kubernetes on any Public & Private Cloud
A complete Kubernetes native disaster recovery solution for backup and restore your volumes and databases in Kubernetes on any public and private clouds.
KubeVault is a Git-Ops ready, production-grade solution for deploying and configuring Hashicorp's Vault on Kubernetes.
Secure HAProxy Ingress Controller for Kubernetes
Kubernetes Configuration Syncer
Kubernetes Authentication WebHook Server
New to KubeDB? Please start here.
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 Redis database.
KubeDB concepts:
The following diagram shows how KubeDB Ops-manager operator reconfigures TLS of a Redis database. Open the image in a new tab to see the enlarged version.
The Reconfiguring Redis/RedisSentinel TLS process consists of the following steps:
At first, a user creates a Redis/RedisSentinel Custom Resource (CR).
KubeDB Community operator watches the Redis and RedisSentinel CR.
When the operator finds a Redis/RedisSentinel CR, it creates required number of StatefulSets and related necessary stuff like appbinding, services, etc.
Then, in order to reconfigure the TLS configuration of the Redis database the user creates a RedisOpsRequest CR with the desired version.
Then, in order to reconfigure the TLS configuration (rotate certificate, update certificate) of the RedisSentinel database the user creates a RedisSentinelOpsRequest CR with the desired version.
KubeDB Enterprise operator watches the RedisOpsRequest and RedisSentinelOpsRequest CR.
When it finds a RedisOpsRequest CR, it halts the Redis object which is referred from the RedisOpsRequest. So, the KubeDB Community operator doesn’t perform any operations on the Redis object during the reconfiguring process.
When it finds a RedisSentinelOpsRequest CR, it halts the RedisSentinel object which is referred from the RedisSentinelOpsRequest. So, the KubeDB Community operator doesn’t perform any operations on the RedisSentinel object during the reconfiguring process.
By looking at the target version from RedisOpsRequest/RedisSentinelOpsRequest CR, KubeDB Enterprise operator will add, remove, update or rotate TLS configuration based on the Ops Request yaml.
After successfully reconfiguring Redis/RedisSentinel object, the KubeDB Enterprise operator resumes the Redis/RedisSentinel object so that the KubeDB Community operator can resume its usual operations.
In the next doc, we are going to show a step-by-step guide on updating of a Redis database using update operation.