Release Status & Compatibility

Krabka is in active greenfield development. This page tracks repository branch statuses, release milestones, and Apache Kafka wire-protocol compatibility targets across the ecosystem.

Repository & Packages Status

Current branches, releases, and target runtimes across krabka-io.

Repository Current Track Readiness Target Runtime Provenance History
krabka-broker
v0.5.4
main @ 7372638 (+21)
Beta / Pre-1.0 Linux / macOS / Win (x86_64, aarch64) SLSA L3 / Sigstore
krabka-protocol
v0.4.0-dev
main @ 07d5be9
In Development Rust (no_std friendly core) Planned (L3) Commit log
krabka-client-rs
v0.4.0-dev
main @ 14d80a1
In Development Rust async tokio Planned (L3) Commit log
krabka-streams-rs
v0.4.0-dev
main @ 375faae
In Development Rust stream runtime Planned (L3) Commit log
krabka-streams-go
v0.1.0-dev
main @ f4b7124
In Development Go 1.22+ / Apache Arrow v17 Planned (L3) Commit log
krabka-streams-java
v1.1.0
main @ e3bd6ce (+10)
Stable Java 17+ / OpenJDK 21 Maven Central (PGP)
krabka-operator
v0.4.0-dev
main @ c77f48b
In Development Kubernetes 1.28+ Planned (L3) Commit log
krabka-connect
v0.4.0-dev
main @ 159c5ad
In Development PostgreSQL 14–18 CDC / Rust Planned (L3) Commit log
krabka-o11y
v0.4.0-dev
main @ 5bcec54
In Development OpenTelemetry / Prometheus Planned (L3) Commit log
krabka-o11y-demo
m20-recovery-fadddcf
main @ 7fd03e9 (+1)
Beta / Pre-1.0 Docker Compose / Grafana 11 Planned (L3)
krabka-cli
v0.4.0
main @ 3e083dd (+2)
Beta / Pre-1.0 CLI (cross-platform binary) Planned (L3)

Apache Kafka Wire Compatibility Targets

Krabka targets byte-level wire compatibility across Kafka release streams, tested against Apache Kafka's protocol specifications and JVM client suites.

Kafka Release Stream Wire Protocol Level KRaft Metadata Layer
Kafka 2.8 Compatible KIP-595 v0
Kafka 3.0 – 3.2 Compatible KIP-595 v1
Kafka 3.3 – 3.6 Compatible KRaft GA (v2)
Kafka 3.7 – 3.9 Compatible KRaft Reconfig
Kafka 4.0 – 4.3 Byte-Exact Target KRaft Native (v4)

Release Artifact Provenance & Cryptographic Verification

Published release artifacts are signed and attested during CI: broker container images are signed keylessly with Sigstore (Cosign), release binaries carry SLSA Level 3 build provenance, and Java packages are signed for Maven Central.

# Verify broker container image signature with Sigstore
cosign verify ghcr.io/krabka-io/krabka-broker:latest \
  --certificate-identity-regexp '^https://github.com/krabka-io/' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

# Verify broker release binary SLSA Level 3 build provenance
gh attestation verify krabka-broker-linux-amd64.tar.gz --repo krabka-io/krabka-broker

# Verify Java client artifact signature
gpg --verify krabka-streams-1.1.0.jar.asc krabka-streams-1.1.0.jar