Currently, each ClowdApp with an otel-collector sidecar requires its own dedicated ConfigMap with a hardcoded naming pattern "<appName>-otel-config". This creates configuration duplication and management overhead when multiple services need the same OpenTelemetry configuration.

In our use case (SWATCH team), we have multiple services in the rhsm-subscriptions environment that all need the same OpenTelemetry configuration:

• `swatch-producer-aws`
• `swatch-producer-azure`
• `swatch-contracts`
• `swatch-billable-usage`
• `swatch-metrics`
• ...

Currently, we must create and maintain 5 separate ConfigMaps with identical content:

1. swatch-producer-aws-otel-config
2. swatch-producer-azure-otel-config
3. swatch-contracts-otel-config
4. swatch-billable-usage-otel-config
5. swatch-metrics-otel-config

Proposed Solution

1. Extend ClowdEnvironment Configuration

apiVersion: cloud.redhat.com/v1alpha1
kind: ClowdEnvironment
metadata:
  name: env-rhsm
spec:
  providers:
    sidecars:
      otelCollector:
        enabled: true
        image: "custom-otel-image:latest"
        configMap: "shared-otel-config"  # NEW: Optional shared ConfigMap name

And always use the "shared-otel-config" config map if sets. Otherwise, keep using the clowder app name based resolution strategy as it does today.

Proposed solution

https://github.com/RedHatInsights/clowder/pull/1268