agent-platform release v3.5.0

Added

• modelManager.networkPolicy.egress (fqdns, cidrs, both empty): further destinations of model-manager on 443 whatever the backend — a private identity provider, a model mirror — the same knob agentManager.networkPolicy.egress already is. cilium: FQDN selectors next to the Hugging Face names and the Ollama endpoint, blocks as toCIDR; kubernetes: the blocks as ipBlocks (names are ignored, the flavor has no FQDN selector). networkPolicy.additionalEgressCIDRs / additionalEgressFQDNs now apply to the model-manager cilium egress for the ollama backend too (they used to render only for the kserve backend; the kubernetes flavor always applied them).
• agent-platform.idpHosts helper in the connectivity chart: the hosts a service that validates tokens itself reaches at its identity provider, from the OAuth provider and the issuer URL — the Dex issuer host, or Google’s accounts.google.com, www.googleapis.com and oauth2.googleapis.com. agent-platform.idpEgress.cilium takes provider next to issuerUrl and renders one toFQDNs rule over those hosts.

Fixed

• The model-manager and agent-manager cilium network policies open egress to Google when the component validates tokens with oauth.provider: google. The IdP egress rule named the issuer host by FQDN and the per-component issuer helpers deliberately return nothing for the google provider, so a Google-backed install rendered no name at all: mcp-oauth’s JWKS fetch (www.googleapis.com/oauth2/v3/certs), userinfo fallback and discovery (accounts.google.com) timed out under policyEnforcementMode: always, muster’s forwarded-token sessions failed and the operator had to add the three hosts to agentManager.networkPolicy.egress.fqdns and open world:443 for model-manager by hand (agent-platform-standalone#106). The rule now derives the hosts from the provider: accounts.google.com (discovery, authorization), www.googleapis.com (JWKS, userinfo) and oauth2.googleapis.com (token, revocation) — the endpoints mcp-oauth’s google provider dials — next to the unchanged cluster entity on 443/10443. The dex render is byte-identical; the kubernetes flavor already opened every public destination on 443 while OAuth is on. make verify-managers asserts both providers and the new egress knob.