Code generation registry + k3s + Helm

Local Kubernetes

The project generates one local k3s environment and one registry, then installs every service through its independent Helm chart.

When to use

Use this reference when generating, reviewing or operating a Service Architect project.

docker-compose.kubernetes.yml starts the local OCI registry, k3s server and isolated Helm client.
Runtime images are built and pushed to the local registry without using latest tags.
The orchestration waits for k3s readiness before installing infrastructure and services.
Generated charts are linted/rendered and releases are verified through probes and metrics.
The same service charts can target production clusters with operator-provided registry, resources, ingress, policies and secrets.

Complete generated Kubernetes command surface.

CommandScopeDescription

make kubernetes-upWorkspace

Build runtime images, start local registry and k3s, deploy Helm releases and verify rollouts.

make kubernetes-buildWorkspace

Build minimal runtime images and publish them to the local OCI registry.

make kubernetes-deployWorkspace

Install project infrastructure and all service Helm releases.

make kubernetes-testWorkspace

Verify rollouts, probes, metrics and the generated cross-service scenario.

make kubernetes-statusWorkspace

Show nodes, pods, Services and Helm releases.

make kubernetes-downWorkspace

Stop local Kubernetes while preserving cluster and registry volumes.

make kubernetes-cleanWorkspace

Remove the cluster, registry and all project cluster volumes.

make k8s-{up,build,deploy,test,status,down,clean}Alias

Short aliases for the corresponding kubernetes-* targets.

make kubernetes-up
make kubernetes-status
make kubernetes-test
make kubernetes-down