agent-platform release v4.40.0

Changed

• The serving slice’s llm-d images come from the llm-d-fast/ prefix, and the pre-pull names that image (giantswarm/agent-platform#568). The well-known LLMInferenceServiceConfigs and the pre-pull DaemonSet named the runtime image as mirrored byte-identically, gsoci.azurecr.io/giantswarm/llm-d-cuda:v0.8.0 — 8.2 GiB compressed in gzip layers of 5.5, 1.4 and 1.0 GB. containerd pulls one HTTPS stream per layer, so the stream carrying the 5.5 GB layer bounded the pull: about 60 MB/s effective, 132–149 s on a fresh pool node where one stream measures 95 MB/s and four 306 MB/s, and the operands pulled beside it ran three to five times slower meanwhile — with the pre-pull in place, the longest cold-start step left. giantswarm/llm-d publishes the same images re-layered under llm-d-fast/ of the same registry path (zstd, llm-d-cuda split into layers of at most 1.2 GB). The meta chart’s kserve-runtime-configs: block now passes kserve.llmisvcConfigs.imageRegistry: gsoci.azurecr.io/giantswarm/llm-d-fast/, so every reference the configs render carries the prefix, and modelServing.prepull.images defaults to gsoci.azurecr.io/giantswarm/llm-d-fast/llm-d-cuda:v0.8.0 in both charts, so the pre-pull warms exactly the image the predictor runs. Going back is two values: the block’s imageRegistry at gsoci.azurecr.io/giantswarm/ (the byte-identical mirror) or ghcr.io/llm-d/ (upstream), and the matching reference in prepull.images. make verify-serving-slice asserts the prefix on the rendered release and that the pre-pull’s reference carries it; verify-gpu-pool leaves the pre-pull DaemonSet out of the golden comparison while origin/main names the mirror’s image. README “The well-known configs” and “Pre-pulling the runtime image”; UPGRADE.md.