failed to mount volume for mtls cert for target allocator

[travisghansen]

Component(s)

collector, target allocator

What happened?

Description

When mtls support is enabled in the operator deployments that do not have target allocator enabled are failing because the secret does not exist:

MountVolume.SetUp failed for volume "default-ta-client-cert" : secret "default-ta-client-cert" not found

The secret isn't being created (presumably) because target allocator isn't enabled on the CR but the deployment is still requiring the mount.

Steps to Reproduce

Enable mtls for TA. Deploy a collector without TA enabled.

Expected Result

No mtls secrets are created, no secrets are required to start the collector.

Actual Result

TLS secrets are not created (as expected when TA is disabled), secret is required by the collector pod to start.

Kubernetes Version

1.31

Operator version

ghcr.io/open-telemetry/opentelemetry-operator/opentelemetry-operator:0.114.1

Collector version

otel/opentelemetry-collector-k8s:0.114.0

Environment information

No response

Log output

No response

Additional context

open-telemetry/opentelemetry-helm-charts#1469