# deploy/ Argo CD delivery of demo-vivek-11 to the lab: the hub's Argo CD pushes it to the `apps-lab` spoke through the argocd-agent, and the hub's public kgateway Gateway forwards to it over Private Link. ``` browser ─► hub pe-gatewayapi (demo-vivek-11.apps.lab…) ─► Private Link ─► spoke pe-gatewayapi-int (demo-vivek-11.int.apps.lab…, port 80) ─► Service demo-vivek-11 ─► pod :8080 ``` | Folder | Applied to | By | |---|---|---| | `argocd/` | lab **hub** | `kubectl apply` once | | `hub/` | lab **hub** | `kubectl apply` once | | `lab/` | lab **spoke** | Argo CD, from this repo. **Generated**: never edit by hand | ## Apply ```bash khub apply -f deploy/argocd/application.yaml khub apply -f deploy/hub/remote-route.yaml ``` ## Rules the Application must keep The lab uses argocd-agent's **destination-based mapping**, and this app belongs to team **demo**. - It lives in namespace **`team-demo`** on the hub: team demo's namespace. The platform creates it. - `project: team-demo`: the platform's AppProject for the team. It accepts Applications only from `team-demo`, and deploys only to spoke namespaces named **`demo-*`** (this app's is `demo-vivek-11`). - `destination.name: apps-lab`: the agent to deploy to, and the routing key. **Never** `destination.server`, which resolves to the hub itself. ## How `lab/` is produced `lab/` is rendered from `score-lab.yaml` by the **Build and Push to ACR (lab)** workflow: it builds the image, renders with the platform's provisioners (`cruciblecoredevacr.azurecr.io/score-provisioners`, version pinned in the workflow), and commits the result. The image tag is the commit that was built. To change what is deployed, change `score-lab.yaml` and run the workflow.