Apache KafkaNative Kafka protocol
ConnectedINTEGRATIONSMeet Kafka
Meet Kafka
where it runs.
Use Kafka’s native protocol for core operations and attach fixed, deployment-owned integrations only where they add trustworthy evidence or control.
KAFKA DISTRIBUTIONS
One core protocol, provider-aware evidence.
Apache Kafka, Bitnami and Strimzi share the Kafka protocol surface. Provider detection and explicit attachments unlock provider-specific context without changing ownership.
Apache Kafka
Use native Admin, Consumer and Producer APIs for metadata, records, groups, ACLs and supported mutations.
Core supportBitnami
Keep Bitnami Helm-managed while BetterKafka uses Kafka protocol operations and displays detected provider evidence.
Core supportStrimzi
Read Kafka, KafkaNodePool and KafkaRebalance status when explicitly attached; create/action KafkaRebalance resources behind guardrails.
Optional attachmentOPTIONAL ENDPOINTS
Integrations stay fixed and server-owned.
Schema Registry
Browse subjects, versions and references; run compatibility dry-runs; register schemas when enabled. Supports Confluent-compatible HTTP APIs.
Kafka Connect
Inspect connectors, tasks, failures, associated topics and redacted configuration; validate configs and guard pause/resume/restart.
Prometheus & ServiceMonitor
Expose BetterKafka metrics and optionally observe broker filesystem capacity from a fixed Prometheus endpoint.
OAuth2 Proxy & Kubernetes
Trust a fixed internal proxy user-info endpoint and optionally resolve authorization through Kubernetes SubjectAccessReview.
Strimzi and Cruise Control: BetterKafka does not call Cruise Control directly. It uses Strimzi’s KafkaRebalance resource workflow, and stopping active movement is not rollback.
DEPLOYMENT-OWNED
Keep endpoints and credentials out of the browser.
Configure integrations through Helm values and Kubernetes Secret references.