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 PerconaXtraDB
, 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 cr 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 the desired x509 certificate which will be renewed and kept up to date. You can learn more details here.
PerconaXtraDB CRD Specification:
KubeDB uses the following cr fields to enable SSL/TLS encryption in PerconaXtraDB
.
spec:
requireSSL
tls:
issuerRef
certificates
Read about the fields in details from perconaxtradb concept,
When, requireSSL
is set, 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 PerconaXtraDB
server, exporter etc. respectively.
The following figure shows how KubeDB
enterprise is used to configure TLS/SSL in PerconaXtraDB. Open the image in a new tab to see the enlarged version.
Deploying PerconaXtraDB with TLS/SSL configuration process consists of the following steps:
At first, a user creates an Issuer/ClusterIssuer
cr.
Then the user creates a PerconaXtraDB
cr.
KubeDB
community operator watches for the PerconaXtraDB
cr.
When it finds one, it creates Secret
, Service
, etc. for the PerconaXtraDB
database.
KubeDB
Ops Manager watches for PerconaXtraDB
(5c), Issuer/ClusterIssuer
(5b), Secret
and Service
(5a).
When it finds all the resources(PerconaXtraDB
, Issuer/ClusterIssuer
, Secret
, Service
), it creates Certificates
by using tls.issuerRef
and tls.certificates
field specification from PerconaXtraDB
cr.
cert-manager
watches for certificates.
When it finds one, it creates certificate secrets tls-secrets
(server, client, exporter secrets, etc.) that hold the actual self-signed certificate.
KubeDB
community operator watches for the Certificate secrets tls-secrets
.
When it finds all the tls-secret, it creates a StatefulSet
so that PerconaXtraDB server is configured with TLS/SSL.
In the next doc, we are going to show a step by step guide on how to configure a PerconaXtraDB
database with TLS/SSL.