redpanda v0.1.0

Messaging

Redpanda — a Kafka-compatible streaming data platform in a single binary (no ZooKeeper/JVM), with a Kafka API, HTTP proxy, and schema registry. Deployed here as a single-node dev-container instance, host-networked with a data volume. A lighter drop-in for Apache Kafka.

nomad-pack run redpanda --registry nomploy

…or one line (add registry + run)

curl -fsSL https://packs.nomploy.com/install.sh | sh -s -- redpanda

Needs nomad-pack on PATH. The script only adds the nomploy registry and runs this pack.

Source ↗ Project ↗ ★ 12.6k ⚑ Report an issue

2 tasks kafka 9092admin 9644proxy 8082schema 8081 1 volume image redpandadata/redpanda:latest tracks :latest image bumped 27 days ago

Variables 13

values.hcl

Save as values.hcl, edit, then run:

nomad-pack run redpanda -f values.hcl --registry nomploy

# The name of the Nomad job.
job_name = "redpanda"

# The Nomad namespace to deploy into.
namespace = "default"

# The datacenters to deploy to.
datacenters = ["*"]

# The Redpanda container image. Pin a tag in production.
image = "redpandadata/redpanda:latest"

# Host port for the Kafka API.
kafka_port = 9092

# Host port for the Redpanda Admin API.
admin_port = 9644

# Host port for the HTTP (Panda) Proxy.
proxy_port = 8082

# Host port for the Schema Registry.
schema_port = 8081

# Host/IP advertised to Kafka clients. 127.0.0.1 works for co-located clients; set this to the node's IP for remote consumers/producers.
advertise_host = "127.0.0.1"

# UID Redpanda runs as. The data volume is chown'd to this at startup.
uid = 101

# Named volume for Redpanda's data (/var/lib/redpanda/data).
data_volume = "redpanda_data"

# Placement constraints. Pin to the node holding the volume. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
constraints = []

# The task resources.
resources = {
    cpu    = 1000
    memory = 1024
  }

Name	Type	Default	Description
job_name	string	"redpanda"	The name of the Nomad job.
namespace	string	"default"	The Nomad namespace to deploy into.
datacenters	list	["*"]	The datacenters to deploy to.
image	string	"redpandadata/redpanda:latest"	The Redpanda container image. Pin a tag in production.
kafka_port	number	9092	Host port for the Kafka API.
admin_port	number	9644	Host port for the Redpanda Admin API.
proxy_port	number	8082	Host port for the HTTP (Panda) Proxy.
schema_port	number	8081	Host port for the Schema Registry.
advertise_host	string	"127.0.0.1"	Host/IP advertised to Kafka clients. 127.0.0.1 works for co-located clients; set this to the node's IP for remote consumers/producers.
uid	number	101	UID Redpanda runs as. The data volume is chown'd to this at startup.
data_volume	string	"redpanda_data"	Named volume for Redpanda's data (/var/lib/redpanda/data).
constraints	list	[]	Placement constraints. Pin to the node holding the volume. On a nomploy cluster: attribute = "$${meta.nomploy_control_plane}", operator = "=", value = "true".
resources	object	{ cpu = 1000 memory = 1024 }	The task resources.

Back up this pack

This pack stores data in one Docker named volume: redpanda_data

restic

# Run on the node hosting this pack. Point restic at your repo first:
#   export RESTIC_REPOSITORY="s3:https://<account>.r2.cloudflarestorage.com/<bucket>"
#   export RESTIC_PASSWORD="<repo-password>"
#   export AWS_ACCESS_KEY_ID=<key>  AWS_SECRET_ACCESS_KEY=<secret>
restic backup \
  /var/lib/docker/volumes/redpanda_data/_data

rclone (sync to S3/R2)

rclone sync /var/lib/docker/volumes/redpanda_data/_data backup:<bucket>/redpanda_data

Paths assume the default Docker volume location (/var/lib/docker/volumes). Restore by stopping the job, restoring files into the same volume, and re-running the pack.

Readme

redpanda

Redpanda — a Kafka-compatible streaming data platform in a single binary (no ZooKeeper, no JVM), with a Kafka API, HTTP (Panda) Proxy, and Schema Registry. A lighter drop-in for Apache Kafka.

Single-node dev-container instance, host-networked with a data volume and a busybox chown init.

Deploy

nomad-pack registry add nomploy https://github.com/Nomploy/nomad-packs
nomad-pack run redpanda --registry=nomploy

Configure

Variable	Default	Description
`kafka_port`	`9092`	Kafka API.
`admin_port`	`9644`	Admin API.
`proxy_port`	`8082`	HTTP (Panda) Proxy.
`schema_port`	`8081`	Schema Registry.
`advertise_host`	`127.0.0.1`	Host advertised to Kafka clients — set to the node IP for remote clients.
`uid`	`101`	User Redpanda runs as; data volume is chown'd to it.
`data_volume`	`redpanda_data`	`/var/lib/redpanda/data`.
`image`	`redpandadata/redpanda:latest`	Image. Pin a tag in production.
`resources`	`{ cpu = 1000, memory = 1024 }`	Task resources.

advertise_host is the classic Kafka footgun: clients connect to the advertised address, so 127.0.0.1 only works for producers/consumers on the same host — set the node IP otherwise. This is a single-node dev-container deployment, not a production cluster. Ports 8081/8082 overlap some other packs' defaults; change them if co-locating. Pin the job with constraints.