Q: Your multi-tenant Kubernetes cluster bill is $120,000/month, but finance cannot attribute costs to specific teams because pods share compute nodes and lack standard metadata. How do you implement OpenCost/Kubecost and enforce cost allocation via Golden Path templates?

Deploy OpenCost in the management cluster configured with AWS Cost and Usage Report (CUR) or public on-demand/spot pricing APIs.

# Helm installation for OpenCost
helm install opencost opencost/opencost \
  --namespace opencost --create-namespace \
  --set opencost.exporter.defaultClusterId=prod-eks-01 \
  --set opencost.prometheus.internal.serviceName=prometheus-k8s

Enforce mandatory labels across all Deployment manifests: `app.kubernetes.io/owner`, `cost-center`, and `environment`.

# Base chart labels
metadata:
  labels:
    cost-center: {{ .Values.costCenter | quote }}
    team: {{ .Values.teamName | quote }}
    environment: {{ .Values.environment | quote }}

Deploy a Kyverno policy that denies deployments in staging and production if the `team` or `cost-center` label is missing.

apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: require-cost-labels
spec:
  validationFailureAction: Enforce
  rules:
    - name: check-team-label
      match: { resources: { kinds: ["Deployment", "StatefulSet"] } }
      validate:
        message: "Deployments must include a 'team' and 'cost-center' label for FinOps tracking."
        pattern:
          metadata:
            labels:
              team: "?*"
              cost-center: "?*"

Expose OpenCost APIs directly in Backstage via the Kubecost plugin, allowing developers to see their team's live daily infrastructure spend.