Contract-driven Kubernetes operator

One declaration. A workload kept true.

v0.1.0 released — image, install bundle, and evidence report, all verdict-checked. The first kube of the Fabric.

Deploy, expose, scale, heal, and evidence a container workload through one stable Kubernetes resource.

Install KubeContainer Read the specification

One CRD for the common caseReconciliation by defaultEvidence attached

kubecontainer.yaml

apiVersion: kubecontainer.unboxd.cloud/v1alpha1
kind: KubeContainer
metadata:
  name: my-app
spec:
  image: ghcr.io/acme/my-app:1.4.2
  port: 8080
  scaling:
    autoscale:
      minReplicas: 2
      maxReplicas: 10
  expose:
    type: Ingress
    host: my-app.example.com

The common workload path, made declarative.

KubeContainer translates intent into concrete Kubernetes resources, then continuously reconciles the cluster until declared and actual state match.

Deploy

Render a production workload from a concise custom resource instead of repeating boilerplate manifests.

Expose

Create the service surface and optional ingress contract from the same declaration.

Scale

Choose fixed replicas or autoscaling semantics without creating ownership conflicts.

Heal

Reconcile drift and restore managed resources when cluster state changes.

Observe

Expose readiness, progress, and degradation through a consistent status contract.

Evidence

Ship verification artifacts and compatibility checks with the operator release.

A contract, not another manifest generator.

The operator owns the rendering. Kubernetes owns scheduling. The reconciliation loop keeps the promise.

1 — Declare

State the intent

Name the image, port, scaling policy, exposure, and health contract.

2 — Render

Define desired state

The operator creates the concrete Deployment, Service, Ingress, and HPA.

3 — Reconcile

Keep it true

Observe, compare, act, and record until the cluster converges.

4 — Prove

Return a verdict

Status, tests, release assets, and compatibility checks show what was delivered.

Published numbers, not adjectives.

Every figure below was produced by a named command against a named commit in a named environment — re-runnable by anyone with the repository. No number ships without its verdict.

9 / 9

Test specs pass

envtest integration suite against a real Kubernetes 1.35 control plane, compat corpus included.

3 / 3

Eval resolution — 100%

Every task in the evaluation registry resolves; the report ships with each release, commit-stamped.

4m 16s

Request → release

Declared release request to published release: tests, lint, vocabulary, evals, image, kind e2e with live traffic.

29 KB

Whole install

One kubectl apply of one 29,282-byte bundle installs the operator on any conformant cluster.

2,178

Lines of Go

The full operator: seven tested guarantees, one CRD, no sidecars, no proprietary wire.

1 day

Empty repo → v0.1.0

First commit and first release share a date in the git record: 2026-06-10.

Commands, commits, environment, and the not-yet-benchmarked list: docs/BENCHMARKS.md.

Kube — the soul of Any'Thing'

A Thing is a body: present, connected perhaps, and inert. The kube is what the wiring never supplied — and the claim is mechanical, not mystical: five parts, each with a verdict.

Declaration

Individuates

This Thing's intent, in schema, distinct from every other's.

Loop

Animates

The Thing acts, keeps itself true, returns when struck down.

Face

Answers at one point

One stable surface where the Thing meets the world.

Record

Remembers

State, history, and evidence — and it survives the instance.

Contract

Answers for itself

Promises with their verdicts named in advance.

The industry gave Things connectivity and called it the Internet of Things — wired bodies, still soulless. Give the Thing a soul and it becomes the Internet of Agents. Built so far, and the only thing this page sells: KubeContainer v0.1.0, the first box to carry one. The Kube as a product of its own is declared, specified, and not yet built — this site publishes that the same way it publishes everything else.

Brand exegesis: KUBE-SPEC §9 · terms defined in the lexicon · mark claimed in NOTICE.

Get started

Install. Apply. Reconcile.

Use the release bundle from the repository, then apply your first KubeContainer resource.

kubectl apply -f https://github.com/unboxd-agency/KubeContainer/releases/download/v0.1.0/install.yaml

kubectl apply -f kubecontainer.yaml

kubectl get kubecontainers

✓

Stable resource surface
One API for the standard container workload lifecycle.

✓

Kubernetes-native ownership
Managed children remain visible and inspectable.

✓

Compatibility discipline
Historical manifests are checked against regression.

✓

Open implementation
Specification, source, governance, and evidence live together.

Package the workload once. Let the loop keep it true.

Open the repository