Helm Chart Repository

One repository URL for every Krabka chart.

Krabka charts are built in the repository that owns each component. The site aggregates them into one Helm repository, so you add a single URL and get every chart from it.

Add the repository:
helm repo add krabka https://krabka-io.github.io/charts
helm repo update
helm search repo krabka

Charts in the index

Chart Source repository What it installs
krabka-operator krabka-io/krabka-operator The Kubernetes operator. It reconciles Kafka, KafkaNodePool, KafkaTopic, KafkaUser, KafkaRebalance and SchemaRegistry resources.
krabka-rebalancer krabka-io/krabka-rebalancer The partition rebalancer. It answers KafkaRebalance requests with a partition assignment plan.
krabka-schema-registry krabka-io/krabka-schema-registry The Confluent-API-compatible schema registry. It stores schemas in the compacted _schemas topic.

index.yaml is the authoritative list. A component repository joins the index as soon as it holds a charts/ directory, so the table above can lag the index by a release.

Install a chart

Install the operator:
helm install krabka-operator krabka/krabka-operator \
  --namespace krabka-system --create-namespace

Verify a chart

The charts carry a Helm provenance file when the release job has the signing key. The public half of that key lives in krabka-io/tooling, at charts/krabka-charts.pub.asc. It is never stored on this site.

Chart signing key
Krabka Charts <charts@krabka.dev>
74A6 7D5C F9AE 199A 45D2 2E42 594B D543 4544 D339

Check this fingerprint against the key you import. Any earlier Krabka chart key is revoked and must not be used.

Verify before install:
# Fetch the chart signing public key from krabka-io/tooling.
curl -fsSLO https://raw.githubusercontent.com/krabka-io/tooling/main/charts/krabka-charts.pub.asc

# Import it, then check the fingerprint against the one published on this
# page before you trust it.
gpg --import krabka-charts.pub.asc
gpg --fingerprint charts@krabka.dev

# Helm needs a binary keyring, not an armored file.
gpg --export charts@krabka.dev > krabka-keyring.gpg

helm install krabka-operator krabka/krabka-operator \
  --verify --keyring ./krabka-keyring.gpg

How the index is built

  1. A scheduled job in this repository walks the krabka-io organisation.
  2. It takes every repository that holds a charts/ directory.
  3. It packages each chart at the version in that repository's workspace Cargo.toml.
  4. It writes one index.yaml over the whole set and commits it.

The index holds the current version of each chart. A renamed chart drops out under its old name on the next run. A component repository can ask for an immediate rebuild by sending a charts-changed repository dispatch to this repository.