Run the orchestrator deploy as the third job of the lab workflow

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-01 17:02:07 +01:00
parent f59c51a823
commit ff767dbfdc
3 changed files with 125 additions and 167 deletions

View File

@@ -14,15 +14,17 @@ browser ─► hub pe-gatewayapi (demo-vivek-11.apps.lab…) ─► Private Link
| Argo CD Application `team-demo/demo-vivek-11` | lab **hub** | the orchestrator, from the workload in `score-lab.yaml` |
| Public route (Backend + HTTPRoute) | lab **hub** | the orchestrator, from the `workload-ingress` resource |
## Workflows
## Workflow
1. **Build and Push to ACR (lab)** builds the image, renders `score-lab.yaml` into `lab/` and commits
it. The image tag is the commit that was built. Argo CD then rolls it out.
2. **Deploy to Orchestrator (lab)** creates or updates the Application and the public route. It is
needed the first time and whenever the hostname, team or repository in `score-lab.yaml` changes.
**Build, Render and Deploy (lab)** runs three jobs for the dispatched commit:
1. **build** the image, tagged with the commit.
2. **render** `score-lab.yaml` into `lab/` and commit it. Argo CD then rolls it out.
3. **deploy** `score-lab.yaml` to the orchestrator, which keeps the Application and the public route
in place. It changes something only when the hostname, team or repository changes.
`lab/` is **generated**: never edit it. To change what is deployed, change `score-lab.yaml` and run
the build workflow. The provisioners version is pinned in that workflow.
the workflow. The provisioners version is pinned in that workflow.
## What `score-lab.yaml` must carry