feat(nfv/ovs-dpdk-sriov): add metricStorage replacement from service-values

The NFV OVS-DPDK-SRIOV validated architecture enables telemetry and
ceilometer via service-values replacements, but metricStorage (Prometheus
monitoring stack) has no replacement — it stays at the base default of
enabled: false regardless of what the deployer sets in service-values.

This adds a kustomize replacement for
telemetry.template.metricStorage.enabled so NFV deployments can toggle
Prometheus metric collection through service-values.yaml, consistent
with how telemetry.enabled and ceilometer.enabled are already handled.

Deployers who want metrics need to add to their service-values.yaml:

  telemetry:
    template:
      metricStorage:
        enabled: true

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Anthony Harivel <aharivel@redhat.com>

Author: aharivel

va/nfv/ovs-dpdk-sriov/kustomization.yaml

@@ -128,3 +128,15 @@ replacements:
           - spec.nova.template.schedulerServiceTemplate.customServiceConfig
         options:
           create: true
+  # Telemetry metric storage toggle for NFV deployments
+  - source:
+      kind: ConfigMap
+      name: service-values
+      fieldPath: data.telemetry.template.metricStorage.enabled
+    targets:
+      - select:
+          kind: OpenStackControlPlane
+        fieldPaths:
+          - spec.telemetry.template.metricStorage.enabled
+        options:
+          create: true