Apache Kafka lets applications publish records into durable event streams that other applications consume at their own pace. It is useful for moving events between services, feeding data pipelines and retaining a sequence that consumers can read again. This entry points to Yolean's Kubernetes manifests, not an official Kafka operator. Their older deployment model must be distinguished from the current broker software and its metadata-management requirements.
Current guidance
The recorded upstream is Yolean/kubernetes-kafka, a community collection of Kubernetes manifests and Kustomize overlays. Its README emphasizes plain manifests and a startup order including ZooKeeper and Kafka. The historical body’s operator language should not imply that this repository is a Kafka operator or an official Apache deployment distribution.
Modern Kafka upgrades require attention to the metadata mode and supported source version. Apache’s versioned upgrade guide describes the transition constraints around KRaft; an old ZooKeeper-based manifest set cannot be upgraded safely by replacing only the broker image. Read the guide for the exact source and target versions before changing storage or metadata configuration.
Inventory broker IDs, advertised listeners, certificates, client authentication, topic replication and persistent volumes. Validate producer and consumer connectivity from every required network, not just a bootstrap probe inside the namespace. Rehearse rolling failure and recovery with representative data, and verify replication health before each step. If moving to an operator, plan how it will adopt or migrate state rather than allowing two reconcilers to manage the same brokers. This review does not benchmark or certify the old manifest set.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub does not mark Yolean/kubernetes-kafka archived or disabled; this does not establish active maintenance, support or compatibility. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Original publication: 2018-09-08T08:38:50+00:00. Preserved for context. Commands, versions, prices and results below reflect the original research.
Enabling everyone to run Apache Kafka on Kubernetes is an important part of our mission to put a streaming platform at the heart of every company. This is why we look forward to releasing an implementation of the Kubernetes Operator API for automated provisioning, management, and operations of Kafka on Kubernetes.
Kafka for Kubernetes
This community seeks to provide:
- Production-worthy Kafka setup for persistent (domain- and ops-) data at small scale.
- Operational knowledge, biased towards resilience over throughput, as Kubernetes manifest.
- A platform for event-driven (streaming!) microservices design using Kubernetes.
Pre Requisites:
- Kubernetes 1.3 with alpha APIs enabled and support for storage classes
- PV support on underlying infrastructure
- Requires at least v2.0.0-beta.1 version of the helm to support dependency management with requirements.yaml
Chart Details
- This chart will do the following:
- Implement a dynamically scalable Kafka cluster using Kubernetes StatefulSets
- Implement a dynamically scalable zookeeper cluster as another Kubernetes StatefulSet required for the Kafka cluster above
- Expose Kafka protocol endpoints via NodePort services (optional)
Extensions
Kafka has a rich ecosystem, with lots of tools. This section is intended to compile all of those tools for which a corresponding Helm chart has already been created.
Schema-registry – A confluent project that provides a serving layer for your metadata. It provides a RESTful interface for storing and retrieving Avro schemas.
Known Limitations
- Only supports storage options that have backends for persistent volume claims (tested mostly on AWS)
- KAFKA_PORT will be created as an envvar and brokers will fail to start when there is a service named Kafka in the same namespace. We work around this be unsetting that envvar unset KAFKA_PORT.
The post Kafka appeared first on kubedex.com.
Sources & further reading
Spotted something that needs another look?
Help improve this page →