agent-platform release v4.28.17

Fixed

• The model pods reach the Hugging Face download CDN: the model-serving egress admits us.aws.cdn.hf.co, three labels under hf.co (giantswarm/agent-platform#522; proof 1 of giantswarm/giantswarm#37639). The connectivity chart’s -model-serving-predictor, -model-serving-llmisvc-workload and -model-serving-download CiliumNetworkPolicies admitted huggingface.co, *.huggingface.co, *.hf.co and *.*.hf.co; Cilium’s * matches one label and never a dot, so the download CDN the Hub redirects every shard request of a Xet-backed repository to (Xet client or not — the LFS path lands on the same host) matched nothing and the download’s SYNs were dropped one second after the DNS proxy had resolved it: with Xet off (#520) the storage-initializer crash-looped on us.aws.cdn.hf.co, with Xet on it hung. modelServing.networkPolicy.huggingFace.fqdns and modelManager.networkPolicy.huggingFace.fqdns gain *.*.*.hf.co; the lists stay a toFQDNs allow-list (no world, no CIDR). tests/verify-model-serving-policies.py (make verify-model-serving-policies) matches the names of the download path — the Hub, the LFS fronts, the Xet fronts, the CDN and a regional sibling — against the rendered patterns of all three policies with Cilium’s rule and keeps out a deeper name and a look-alike domain, so a new host shape fails the render, not a download on an installation. The modelServing.policies.env comment of #520 is corrected: Xet off keeps the initializer on one host path that fails fast on a policy drop; it is not what reaches the CDN.