cloudivision

01 · The problem

Make the workflow clear.

Build execution and environment deployment need distinct ownership. A CI runner with broad cluster permissions makes that boundary difficult to review and recover.

02 · The approach

Give each part a job.

Source events create build resources in Kubernetes. Controllers reconcile isolated runner Jobs, which produce image evidence. A deployment repository records the release intent, and Argo CD or Flux reconciles the environment.

1. 1Source event
2. 2BuildRun resource
3. 3Runner Job
4. 4Image + GitOps commit
5. 5Argo CD / Flux

03 · A practical starting point

Try the documented workflow.

./hack/kind-create.sh
./hack/kind-load-images.sh
./hack/install-dev.sh

Repository quickstart commands create a local kind environment. Docker, kind, kubectl, Helm, Go, and Node are prerequisites.

04 · The result

Something you can inspect.

The project documents a kind quickstart, an operations UI, and a credential-free example. Its published alpha has explicit readiness gates; development authentication settings require review before evaluating a production installation.