Skip to content
Intropy
Run

intropy.run

A staging or production runtime needs a real Kubernetes cluster and the backing services your integrations use. For a first test, use k3d: it runs a Kubernetes cluster inside Docker, can be created from the CLI, and can be deleted when the test is done.

Start with an empty cluster. Add Dapr and only the fixtures your System needs. Then build local images, import them into k3d, render the manifests, and apply them to the cluster.

Terminal window
k3d cluster create intropy
dapr init -k
kubectl create namespace integration
DOCKER HOSTk3d clustercreated by CLIrunsKUBERNETES IN DOCKERLOCAL · DISPOSABLERUNTIME PREREQUISITESDapr runtimefixturesnamespaceLOCAL WORKSPACEIntropy SystemComponents · topologylocal imagesimported into k3dbuildimportSYSTEM NAMESPACEDeploymentCronJobDapr Componentsrendered manifestsapply locallyrenderapplylogs · traces · Kubernetes resources
FIG R1The local runtime path: create a k3d cluster, add Dapr and fixtures, import local images, apply rendered manifests, and inspect the deployed System.

Start here

Section titled “Start here”

Local k3d cluster

Create a plain k3d cluster, install Dapr, and add only the fixtures your System needs.

Render to a local cluster

Rendered manifests

Render a System into Kubernetes YAML for a local cluster, choose port fixtures, and see what resources are emitted.

Render to a local cluster

Observability

Read logs, traces, and metrics from the local runtime. Wire a Component’s host to an OTLP exporter to collect all three.

Configure telemetry

Later

Section titled “Later”

Runtime concepts

The model behind the local path: topology, ports, manifests, and environment-owned configuration.

Runtime concepts