🐛 Fix Helm ownership collision for prometheus-ca ConfigMap in shared namespace

When multiple WVA releases are installed on the same cluster from different
namespaces, they both try to create a ConfigMap with the same name in the
shared openshift-user-workload-monitoring namespace. Helm's ownership
annotation (meta.helm.sh/release-namespace) rejects the second install.

Use the clusterResourceName helper (which appends .Release.Namespace) instead
of fullname to make the ConfigMap name unique per release namespace. This is
consistent with how all ClusterRoles and ClusterRoleBindings in the chart
already handle multi-namespace uniqueness.

Signed-off-by: Andy Anderson <andy@clubanderson.com>
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Signed-off-by: Andrew Anderson <andy@clubanderson.com>

Author: clubanderson

charts/workload-variant-autoscaler/templates/prometheus-ca-configmap-prom.yaml

@@ -2,7 +2,7 @@
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  name: {{ include "workload-variant-autoscaler.fullname" . }}-prometheus-ca
+  name: {{ include "workload-variant-autoscaler.clusterResourceName" . }}-prometheus-ca
   namespace: {{ .Values.wva.prometheus.monitoringNamespace }}
   labels:
     {{- include "workload-variant-autoscaler.labels" . | nindent 4 }}