ClusterForge

01 · The problem

Make the workflow clear.

Repeated platform setup needs reusable conventions while preserving the infrastructure files an operator must inspect, change, and review.

02 · The approach

Give each part a job.

A Go CLI generates projects and environments from focused foundation, orchestrator, platform, and workload modules. Generated Terraform remains visible. Planning, policy checks, and operational evidence sit alongside explicit apply workflows.

1. 1Project + environment
2. 2Go CLI
3. 3Readable Terraform
4. 4Saved plan + review
5. 5Container platform

03 · A practical starting point

Try the documented workflow.

cf --non-interactive wizard --defaults
cf generate dev
cf init dev
cf plan dev --out .cf/plans/dev.tfplan --risk-summary

The credential-free quickstart targets an existing Kubernetes context. These commands generate and plan infrastructure; review the project documentation before applying it.

04 · The result

Something you can inspect.

The repository includes modules, examples, installation guidance, and a local Kubernetes workflow. Platform coverage has distinct maturity levels; each real cloud environment still needs its own network, IAM, deployment, and recovery evidence.