agent-platform release v4.66.4

Changed

• The Substrate data plane follows the Substrate release: the meta chart no longer forwards substrate.images.agentgateway, and a Substrate patch no longer turns this chart red (giantswarm/agent-platform#654). components.substrate.versionRange admits the line’s patches so installations float onto them, and each Substrate release stamps the agentgateway build its router and egress config was written for. The forwarded pin won over that default, and make verify-substrate-images required it to equal every admitted release’s: Substrate 1.0.2 and 1.0.3 each turned main and every open pull request red until a pin PR merged, and an installation that floated onto the patch first ran the older data plane against the newer config. Now the release’s own default rules. The check requires every admitted release’s third-party defaults to be published gsoci references, images.agentgateway a release of the agentgateway line under agentgateway.proxy.image’s repository. It refuses a forwarded agentgateway and holds the remaining pins (postgres, rustfs, awsCli) to the floor’s defaults only. At the 1.0.3 floor the rendered substrate release is unchanged (its default is the 2.1.2 the pin named), so nothing rolls. The platform’s own controller and data planes stay named in full (agentgateway.controller.image, agentgateway.proxy.image); they do not configure the atenet gateways, which run the release’s static config. An installation that sets substrate.images.agentgateway itself (a mirror) keeps its value and holds its data plane there. README “The chart’s third-party images”.