agent-platform release v4.120.1

muster’s egress on the kubernetes flavour reaches its MCP backends and DNS (giantswarm/agent-platform#840). Every NetworkPolicy that selects muster makes its egress default-deny beyond their union, and -muster-to-agent-manager (and -otlp-egress) select it; networkPolicy.musterInClusterMcpPorts rendered only a CiliumNetworkPolicy, so on a cluster without Cilium muster’s reach to the in-cluster MCP backends rested on muster’s own chart policy, which opens in-cluster egress on 80/443 only. The kubernetes flavour now renders <muster>-mcp-egress as a NetworkPolicy: DNS, musterInClusterMcpPorts to every pod of the cluster (the counterpart of the cilium flavour’s cluster entity) and each networkPolicy.mcpBackends entry on its ports. make verify-mcp-backend-netpol asserts that the union of the policies selecting muster reaches agent-manager, each backend and DNS.