Customers deploying Valkey Operator on Kubernetes have raised concerns about the mandatory use of cert-manager in the setup.
In certain environments, Cert-Manager is not preferred due to:
As a result, customers may request an option to disable Cert-Manager and are seeking clarity on why it is required.
Additionally, there is a need to understand what data is transmitted through the Valkey Operator webhook during resource creation or updates.
1. Webhook Data Transmission Clarification
When a user creates or updates a Valkey Custom Resource:
No user application data or runtime data is transmitted—only configuration metadata required for validation and mutation.
2. Why Cert-Manager is Required
Kubernetes enforces a strict rule:
All Admission Webhooks must be served over HTTPS
Because of this:
To automate certificate provisioning and lifecycle management, the operator relies on:
Without a certificate:
- At present, Cert-Manager is a required dependency for Valkey Operator due to Kubernetes webhook security requirements.
- There is no supported option to disable Cert-Manager today.
- R&D is checking the feasibility of disabling Cert-Manager which is under evaluation.