How-To Guides

Task-focused operational runbooks — "I need to do X, what are the exact commands?" These complement the deployment guide (which builds the platform once) and the Knowledge Base (which explains recurring behaviours). Use these when you're changing a running platform.

Guide	Use when you need to…
Repo Sanitization — Dev → Lab	Push a dev repo to the lab/customer GitLab — remove cloud credentials, ADO configs, internal tooling, prod env files, and source code that doesn't belong in a cluster repo. Covers the 6-repo inventory with a per-repo checklist.
Add a New Add-on Application to cluster-addons	The everyday task — drop one more Helm chart or manifest set into the existing cluster-addons ApplicationSet. Pure GitOps: two files + a push, auto-named as the Application modgpt.cluster-addons.<name>.
Create a New App Group from Scratch	Stand up a brand-new ApplicationSet + its AppProject, repo credentials, and root Application — e.g. onboard a new app group (modgpt.<app>.*) or re-bootstrap on a fresh cluster.
Update ArgoCD Config (Projects, ApplicationSets, Applications)	Change the GitOps control plane that already exists — add a repo to the modgpt AppProject, edit the cluster-addons ApplicationSet, upgrade an add-on, or force a reconcile. Explains which changes are manual vs GitOps.

The golden rule of this platform

The app layer is GitOps; the bootstrap layer is manual. If you edit a file under apps/, values/, infra/, or bootstrap/ and push to GitLab, ArgoCD applies it. If you need to change the AppProject or the root Application, those live only in the cluster — you apply them by hand. The guides here tell you which is which for every object.