From our blog: No Kafka data platform without ownership Why federated ownership underpins governance and policy enforcement at scale.
What you can control
Traffic Control Policies work as that validate and enforce rules on: Configuration policies- Broker and topic configuration changes
- Topic creation parameters (replication factor, partition count)
- Schema ID requirements
- Producer throughput limits
- Consumer fetch rate limits
- Offset commit frequency
- Consumer group join frequency
- Connection attempt limits
- Read-only topics
- Required client IDs
- Consumer group restrictions
- Message header removal
Benefits
- Prevent misconfiguration: stop teams from creating topics with dangerous settings
- Protect cluster performance: rate limit clients before they impact others
- Enforce standards: require schema IDs, client IDs, or other organizational policies
- Gradual rollout: apply policies per or
Available policies
- Alter broker config
- Alter topic config
- ClientId required
- Consumer group policy
- Create topic policy
- Fetch policy
- Limit commit offset
- Limit connection attempts
- Limit join group
- Limit producer rate
- Produce requests
- Read-only topic
- Remove message headers
- Schema ID required