cert-manager Requirement in Tanzu Postgres for Kubernetes When Using Custom Certificates
search cancel

cert-manager Requirement in Tanzu Postgres for Kubernetes When Using Custom Certificates

book

Article ID: 425383

calendar_today

Updated On:

Products

VMware Tanzu for Postgres VMware Tanzu Data Suite VMware Tanzu Data Suite VMware Tanzu Greenplum VMware Tanzu Greenplum / Gemfire

Issue/Introduction

Users deploying Tanzu Postgres for Kubernetes (postgres-operator) often check whether cert-manager can be removed when using custom, user-provided TLS certificates.

 

Cause

Although the postgres-operator allows users to:

- Supply their own TLS certificates

- Reference pre-created Kubernetes secrets

the operator still depends on cert-manager being installed because:

- cert-manager CRDs and APIs are used internally by the operator

- Admission webhooks and certificate reconciliation logic rely on cert-manager

- Even when custom certs are provided, the operator checks and interacts with cert-manager components

This makes cert-manager a runtime dependency, not just a certificate issuer.

Resolution

- cert-manager must be installed in the cluster at all times

- Custom certificates do not eliminate the cert-manager requirement. cert-manager is mandatory even if it is not actively issuing certificates.

- You can still use user-provided certificates by creating TLS secrets manually and referencing them in the Postgres cluster spec