First Cluster Workflow
The repository suggests a clean product story: developers should not need to know every infrastructure detail before asking the platform to create or update a cluster.
End-to-end journey
- A developer enters the Backstage portal.
- They open a scaffolder workflow such as cluster provisioning, scaling, or upgrade.
- The template generates GitOps artifacts and metadata.
- GitHub Actions validate the change.
- ArgoCD reconciles the approved change onto the correct management cluster.
- Cluster API providers create or update workload infrastructure in the target cloud.
The important abstraction
Developers interact with a platform workflow, not with raw infrastructure manifests. That abstraction is the main value of the product.
Where the workflow lives in this repo
- Templates live in
templates/. - GitOps examples live in
gitops-repo-structure/. - Catalog data lives in
catalog/. - Frontend routes and pages live in
packages/app/src/.
What to inspect if something feels broken
| Symptom | First place to inspect |
|---|---|
| Workflow missing in UI | templates/ and frontend routes |
| Generated manifest shape is wrong | template skeleton files |
| Docs page does not match behavior | Docusaurus docs and TechDocs references |
| Cluster not reconciling | GitOps flow, ArgoCD registration, management cluster inputs |