// the find
confluentinc/cp-all-in-one
docker-compose.yml files for cp-all-in-one , cp-all-in-one-community, cp-all-in-one-cloud, Apache Kafka Confluent Platform
Official Confluent docker-compose files for spinning up the full Confluent Platform stack locally — broker, Schema Registry, Connect, Control Center, ksqlDB, and Flink, all wired together. Useful for developers who need a realistic Kafka environment without a cloud account, or want to test against the enterprise feature set before committing to Confluent Cloud.
Covers four distinct deployment shapes in one repo (enterprise, community, cloud-connected, OAuth/Keycloak), which means you can test the same app against different licensing tiers without hunting for separate configs. The GitHub Actions integration is a practical touch — you can spin up a real broker in CI without managing your own Kafka infrastructure. KRaft mode support means you're not dragging along ZooKeeper, which alone saves 2–3 containers and a lot of config noise. The OAuth variant ships a full Keycloak setup with helper scripts for certificate init and token issuance, which is rare to find pre-wired.
These compose files pull the full Confluent Platform images, which are large and require accepting Confluent's license for the enterprise variant — if you just want vanilla Kafka for a side project, this is overkill and the license terms will surprise you. The repo is essentially documentation-as-YAML with very little automation around version updates; branches are cut per CP release (7.7.1-post, etc.) but there's no clear signal on which branch is current for a given use case. The Prometheus and alertmanager configs are committed as pre-generated files in vol/config, meaning they'll silently drift from what the compose setup actually runs unless you know to regenerate them. No health-check or startup-order guarantees in the compose files — Control Center frequently beats the broker on first start and you get a confusing failed state.