Skip to content

Latest commit

 

History

History
92 lines (63 loc) · 2.97 KB

secure.md

File metadata and controls

92 lines (63 loc) · 2.97 KB
Raw

Secure MongoDBCommunity Resources

Table of Contents

Secure MongoDBCommunity Resource Connections using TLS

You can configure the MongoDB Community Kubernetes Operator to use TLS certificates to encrypt traffic between:

  • MongoDB hosts in a replica set, and
  • Client applications and MongoDB deployments.

The Operator automates TLS configuration through its integration with cert-manager, a certificate management tool for Kubernetes.

Prerequisites

Before you secure MongoDBCommunity resource connections using TLS, you must Create a database user to authenticate to your MongoDBCommunity resource.

Procedure

To secure connections to MongoDBCommunity resources with TLS using cert-manager:

  1. Add the cert-manager repository to your helm repository list and ensure it's up to date:

    helm repo add jetstack https://charts.jetstack.io
helm repo update

  2. Install cert-manager:

    helm install cert-manager jetstack/cert-manager --namespace cert-manager \ 
--create-namespace --set installCRDs=true

  3. Create a TLS-secured MongoDBCommunity resource:

    helm upgrade --install community-operator mongodb/community-operator \
--namespace mongodb --set resource.tls.useCertManager=true \
--set createResource=true --set resource.tls.enabled=true \
--set namespace=mongodb --create-namespace

This creates a resource secured with TLS and generates the necessary certificates with cert-manager according to the values specified in the values.yaml file in the Community Kubernetes Operator chart repository.

cert-manager automatically reissues certificates according to the value of resource.tls.certManager.renewCertBefore. To alter the reissuance interval, either:

  • Set resource.tls.certManager.renewCertBefore in values.yaml to the desired interval in hours before running helm upgrade

  • Set spec.renewBefore in the Certificate resource file generated by cert-manager to the desired interval in hours after running helm upgrade

  1. Test your connection over TLS by

    • Connecting to a mongod container using kubectl:
    kubectl exec -it mongodb-replica-set -c mongod -- bash

    Where mongodb-replica-set is the name of your MongoDBCommunity resource

    • Then, use mongosh to connect over TLS:
    mongosh --tls --tlsCAFile /var/lib/tls/ca/ca.crt --tlsCertificateKeyFile \
/var/lib/tls/server/*.pem \ 
--host <mongodb-replica-set>.<mongodb-replica-set>-svc.<namespace>.svc.cluster.local

    Where mongodb-replica-set is the name of your MongoDBCommunity resource and namespace is the namespace of your deployment.