Clouds covered
3
Azure, AWS, GCP
Morgan Stanley Kubernetes as a Service
The developer guide for a Backstage-powered Kubernetes platform.
Learn how the product is structured, how the workflows map to GitOps, and where to make the right changes in the repo without hunting through the codebase first.
WorkflowsArchitectureTemplatesGitOpsOperations
BackstageGitOpsCluster API
Cluster inventory across AKS, EKS, and GKE
Self-service scaffolder templates for Day 1 and Day 2 operations
GitOps repository conventions and ArgoCD reconciliation model
Monitoring, security, cost, DORA, support, and add-on management
Primary workflows
6
Provision, scale, upgrade, destroy, namespace, add-ons
App surfaces
10+
Clusters, docs, tools, support, AI, monitoring, cost, security
Documentation journeys
Start from your task, not from a folder tree.
Recommended path
Understand the platform
See how Backstage, Cluster API, ArgoCD, and cloud providers fit together in the KaaS operating model.
Open guideRecommended path
Ship your first cluster change
Follow the developer workflow from local setup to a cluster provisioning or Day 2 operation request.
Open guideRecommended path
Navigate the repo fast
Use the repository map to find templates, catalog data, frontend surfaces, and GitOps examples without guesswork.
Open guideWhy this exists
The repo already contains strong building blocks. This site makes them legible.
Product-aware information architecture
The navigation mirrors the actual product surface in the Backstage app: clusters, workflows, docs, tools, support, security, monitoring, cost, and GitOps-backed templates.
Developer-first reference paths
Repo structure, templates, and deployment flow are documented as operating assets, not marketing content. That makes the site useful during implementation, onboarding, and review.
Designed to publish on GitHub Pages
The site is isolated from the Backstage runtime, versionable in this repo, and deployable from `main` through a dedicated Pages workflow.