Partition Count Bounds

Topics must have between 1 and 200 partitions (defaults).

“Somebody created a topic with arbitrary number of partitions.”

Rationale

Over-provisioning partitions slows rebalances and inflates controller metadata. Under-provisioning caps throughput. Bounds force teams to justify outliers.

Pattern

1 ≤ partitions ≤ 200

Examples

Parameters

Governs

This policy relates to the following Kafka configuration keys:

• num.partitions

Implementation

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

# Conduktor self-service ResourcePolicy
# Schema: https://docs.conduktor.io/platform/reference/resource-reference/self-service/#resourcepolicy
---
apiVersion: self-serve/v1
kind: ResourcePolicy
metadata:
  name: partition-count-bounds
spec:
  targetKind: Topic
  description: Topics must have between 1 and 200 partitions
  rules:
    - condition: spec.partitions >= 1 && spec.partitions <= 200
      errorMessage: "Partitions must be between 1 and 200 (request an override for outliers)"

Related policies

• Partition Count Must Be Consumer-Parallelism Aligned
• Per-Tenant Partition Budget