Topic Must Declare owner and data-criticality Labels

Every topic must carry `owner` (email) and `data-criticality` (C0..C3) labels.

Rationale

The single most repeated platform-engineer complaint: "we have 4,000 topics and nobody knows who owns half of them." Without an `owner` label at create-time you cannot run a stale-topic sweep, you cannot page anyone during incidents, and chargeback rollup is impossible. `data-criticality` (C0/C1/C2/C3) drives alerting thresholds downstream.

Pattern

labels.owner matches email AND labels["data-criticality"] in [C0, C1, C2, C3]

Examples

Parameters

Implementation

Drop this YAML into Conduktor Console as a ResourcePolicy, then link it from an ApplicationInstance, Application, or KafkaCluster.

# Conduktor self-service ResourcePolicy
# metadata.labels is optional — has(...) guards avoid silent rejection.
---
apiVersion: self-serve/v1
kind: ResourcePolicy
metadata:
  name: topic-owner-label-required
spec:
  targetKind: Topic
  description: every topic must carry owner (email) and data-criticality (C0..C3) labels
  rules:
    - condition: 'has(metadata.labels.owner) && metadata.labels.owner.matches("^[a-z0-9._-]+@[a-z0-9.-]+\\.[a-z]{2,}$") && "data-criticality" in metadata.labels && metadata.labels["data-criticality"] in ["C0", "C1", "C2", "C3"]'
      errorMessage: "metadata.labels.owner (email) and metadata.labels[\"data-criticality\"] (C0..C3) are required — unowned topics become stale and unpageable"

Related policies

• Topic Name Must Include Declared domain Label as Prefix
• Data Criticality Label Required
• Data Residency Label Required
• Cost-Center Label Required (Chargeback)
• Topic Owner Label Must Be a Team Slug