jesuscabrera1984/redpanda-sasl-bootstrap repository overview

⁠Redpanda SASL Bootstrap

This image provides a secure, reproducible Redpanda setup with SASL/SCRAM authentication enabled the right way.

It is designed to avoid the most common Redpanda / Kafka security pitfalls by enforcing explicit configuration instead of unsafe defaults.

⁠What this image does

•	Enables SASL/SCRAM authentication
•	Disables automatic topic creation
•	Creates users, topics and ACLs explicitly during bootstrap
•	Applies fine-grained permissions for producers and consumers
•	Uses an idempotent startup process (safe to restart)

⁠What this image does NOT do

•	It does not auto-create topics on produce/consume
•	It does not rely on insecure defaults
•	It does not hide Kafka security complexity behind magic

⁠Intended use cases

•	Local development environments
•	CI pipelines
•	Staging clusters
•	Teams that want deterministic Kafka behavior

This image exists because getting Redpanda security right is hard, and the correct order of operations is rarely documented.

⁠Quick start (example)

See the section below for a minimal docker run example.

⁠Docker run

docker run -d
--name redpanda-0
--network siscom-network
-v redpanda_data:/var/lib/redpanda
-p 9092:9092
-p 9644:9644
-e REDPANDA_SUPERUSER_NAME=super_user
-e REDPANDA_SUPERUSER_PASSWORD=secretpassword
-e PRODUCER_USER_NAME=producer_user
-e PRODUCER_USER_PASSWORD=producerpassword
-e CONSUMER_USER_NAME=consumer_user
-e CONSUMER_USER_PASSWORD=consumerpassword
jesuscabrera1984/redpanda-sasl-bootstrap:latest

After startup completes, you can verify the cluster:

docker exec -it redpanda
rpk cluster info
--brokers localhost:9092
-X sasl.mechanism=SCRAM-SHA-256
-X user=superuser
-X pass=secretpassword

NOTE This image is intentionally opinionated. If you expect Kafka to auto-create topics or bypass ACLs, this image is not for you.