You are looking at the documentation of a prior release. To read the documentation of the latest release, please
visit here.
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.
Prerequisite : To configure TLS/SSL in Kafka
, KubeDB
uses cert-manager
to issue certificates. So first you have to make sure that the cluster has cert-manager
installed. To install cert-manager
in your cluster following steps here.
To issue a certificate, the following crd of cert-manager
is used:
Issuer/ClusterIssuer
: Issuers, and ClusterIssuers represent certificate authorities (CAs) that are able to generate signed certificates by honoring certificate signing requests. All cert-manager certificates require a referenced issuer that is in a ready condition to attempt to honor the request. You can learn more details here.
Certificate
: cert-manager
has the concept of Certificates that define a desired x509 certificate which will be renewed and kept up to date. You can learn more details here.
Kafka CRD Specification :
KubeDB uses following crd fields to enable SSL/TLS encryption in Kafka
.
spec:
enableSSL
tls:
issuerRef
certificates
Read about the fields in details from kafka concept,
When, enableSSL
is set to true
, the users must specify the tls.issuerRef
field. KubeDB
uses the issuer
or clusterIssuer
referenced in the tls.issuerRef
field, and the certificate specs provided in tls.certificate
to generate certificate secrets using Issuer/ClusterIssuers
specification. These certificates secrets including ca.crt
, tls.crt
and tls.key
etc. are used to configure kafka
server and clients.
The following figure shows how KubeDB
enterprise used to configure TLS/SSL in Kafka. Open the image in a new tab to see the enlarged version.
Deploying Kafka with TLS/SSL configuration process consists of the following steps:
At first, a user creates a Issuer/ClusterIssuer
cr.
Then the user creates a Kafka
cr which refers to the Issuer/ClusterIssuer
cr that the user created in the previous step.
KubeDB
Provisioner operator watches for the Kafka
cr.
When it finds one, it creates Secret
, Service
, etc. for the Kafka
database.
KubeDB
Ops-manager operator watches for Kafka
(5c), Issuer/ClusterIssuer
(5b), Secret
and Service
(5a).
When it finds all the resources(Kafka
, Issuer/ClusterIssuer
, Secret
, Service
), it creates Certificates
by using tls.issuerRef
and tls.certificates
field specification from Kafka
cr.
cert-manager
watches for certificates.
When it finds one, it creates certificate secrets tls-secrets
(server, client, exporter secrets etc.) that holds the actual certificate signed by the CA.
KubeDB
Provisioner operator watches for the Certificate secrets tls-secrets
.
When it finds all the tls-secret, it creates the related StatefulSets
so that Kafka database can be configured with TLS/SSL.
In the next doc, we are going to show a step-by-step guide on how to configure a Kafka
cluster with TLS/SSL.