Releasing: DTAP, blue/green, canary, environments and fallback – Multi-agent systems (AI-500, lesson 30)

What you learn in this lesson

explain what Learn's default "always the latest version" means for a team of prompt agents, and fix (pin) a version in every environment

build a canary of the agent version in the code of the orchestration, because Learn names no percentage distribution for prompt agents, and calculate its limits at low load

switch the app `app-gruppenreisen` blue/green over Container Apps revisions and explain why weights alone do not switch a queue consumer

describe four environments (DTAP) from the same files with names, versions and gates per stage

plan a fallback for agent version and app revision separately

The pruefer of the group-travel team gets new instructions. A developer saves them in the portal. What happens to the runs of the trip planners in the next minutes? According to Learn: As soon as the new version exists, the agent's endpoint serves it, if nobody has fixed anything. F-07 separates two things: the app is switched blue/green, the agent version by canary. The lesson asks: How does a change get into production without hitting all runs at once, and how do you get back?

Prior knowledge. "K3, lesson 3.7.6" (approvals before the deploy) shows stages, approvals, the same image in several stages and the rollback of a Container Apps revision, "K3, lesson 3.2.6" (environments) parameter files per environment. "AI-103, lesson 1.2" left open how to set an agent version by code; this lesson answers that for what Learn shows today. "AI track, lesson T10.4" shows shadow run and switching by configuration. New: Learn's default, the distribution over runs and an app that reads from a queue.

New in this lesson. (1) The Foundry resource is called ai-nordlicht-<umgebung> per environment (refines M-09: Learn demands worldwide uniqueness for the subdomain). (2) Per agent three configuration values: stabil, kandidat, prozent. (3) Every trace carries agentenversion and apprevision (adds to the span from 1.4). (4) app-gruppenreisen has an internal ingress only for health check and label test; the work still arrives through anfragen (M-10). (5) A switch Verbraucher:Aktiv decides whether a revision reads from anfragen.

The requirement

All numbers are assumptions of the task.

No.	Requirement	Type	Measure	Weight	Source
4.6-01	A new agent version serves no run before it is approved.	R	0 runs on unchecked versions	Must	F-07
4.6-02	A run uses every agent from start to end in one version.	R	0 runs with a version change	Must	M-03
4.6-03	The candidate gets shares of the runs in stages.	F	10, 25, 50, 100 %	Should	F-07
4.6-04	Fallback to the stable version.	Q	under 15 minutes	Must	AI-103 1.2-05
4.6-05	When the app is switched, no run is lost without a trace.	R	0	Must	M-10
4.6-06	Four environments arise from the same files.	F	only parameters differ	Must	M-09

This lesson belongs to course AI-500

You will see the rest of this lesson and its video once you have bought the course. The goals above show what you learn here.

€129.00

incl. VAT, one-time payment

Access to all of the course's lessons with their exercises, solutions and videos on this site, for 24 months from the purchase. A self-study course: no tutoring, no exams or grading by us, and no certificate.

Withdraw from contract here