[Feature]: Operator to support multiple deployments in parallel #10405

Is there an existing issue already for this feature request/idea?

• I have searched for an existing issue, and could not find anything. I believe this is a new feature request to be evaluated.

What problem is this feature going to solve? Why should it be added?

When deploying multiple instances of the CloudNativePG operator in the same cluster (e.g. for staging environments), the MutatingWebhookConfiguration and ValidatingWebhookConfiguration resource names are hardcoded to cnpg-mutating-webhook-configuration and cnpg-validating-webhook-configuration. Since these are cluster-scoped resources, multiple operator deployments will collide on them.

Describe the solution you'd like

Operator to support being deployed in parallel into multiple namespaces without the webhooks colliding.

Solution ideas:

1. Append the namespace to the name or some unique identifier to the webhook name when namespace mode is in use
2. Configurable names for the webhook:
   Add two new fields to configuration. Data, following the existing pattern of other configurable names like OPERATOR_NAMESPACE and WATCH_NAMESPACE:

MutatingWebhookConfigurationName  string `json:"mutatingWebhookConfigurationName"  env:"MUTATING_WEBHOOK_CONFIGURATION_NAME"`
ValidatingWebhookConfigurationName string `json:"validatingWebhookConfigurationName" env:"VALIDATING_WEBHOOK_CONFIGURATION_NAME"`

These can be set via environment variables, or through the operator ConfigMap/Secret. The existing hardcoded values would remain as defaults when not configured.

Describe alternatives you've considered

• Kustomize namePrefix: Renames resources at the manifest level but breaks the operator since the hardcoded names in the binary no longer match.
• External CA injection (cert-manager or OLM): Requires a CA injector to patch the caBundle field, which is not always available.

Additional context

No response

Backport?

Yes

Are you willing to actively contribute to this feature?

Yes

Code of Conduct

• I agree to follow this project's Code of Conduct