Files
demo-vivek-11/deploy

deploy/

How demo-vivek-11 reaches the lab. Everything starts from score-lab.yaml; nothing here is written by hand.

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
What Where Produced by
Deployment, Service, HTTPRoute, NetworkPolicy (lab/) lab spoke score-k8s with the platform's provisioners, delivered by Argo CD
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

  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.

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.

What score-lab.yaml must carry

  • metadata.annotations["crucible.kyndryl.com/team"]: the owning team (demo). The Application is created in team-demo, and may deploy only to spoke namespaces named demo-*.
  • metadata.annotations["crucible.kyndryl.com/repo-url"]: this repository.
  • Readiness and liveness probes, required by the platform's policy check.