Kafka
You’ll get a durable message / event stream for apps in an environment.
Choose this when
- Apps need producers and consumers on a shared event bus
- You want Kafka managed as a ready-made app instead of a custom image
What you get
- Kafka in your environment
- Internal endpoints for producers and consumers
- Disk / storage and copies for retention and capacity
Options
| Option | Purpose |
|---|---|
| Environment | Where Kafka runs |
| Access | Prefer internal-only unless clients outside the cluster need to connect |
| Disk / storage | Retention capacity |
| Copies | Capacity / redundancy (use at least 3 for production) |
Connect
Copy bootstrap addresses from the app Public access page.
- In the same cluster:
{app-name}-kafka-bootstrap.{environment}.svc:9092 - From the public internet or another cluster:
{cluster-public-ip}:{node-port}
Set the cluster public IP in Cluster Settings before you enable external access. Kafka then advertises that address on every broker NodePort, so clients do not need node private IPs. Ingress is not used for Kafka (it is a TCP protocol, not HTTP).
After deploy
Size disk for retention before production. Full deploy steps: How to use ready-made apps.