[vvoytovych]

Summary

The e2e environment runs Milo v0.32.5, and production runs v0.36.5. Before v0.36.3, Milo's OpenAPI v2 names its identity models by Go path, which kubectl's v2 parser cannot resolve (milo-os/milo#838). kubectl reads v2 while Milo does not serve v3 yet, so ipam-fixtures stopped on SchemaError(go.miloapis.com/milo/pkg/apis/identity/v1alpha1.Passkey.status): unknown model in reference in 44 of 328 e2e attempts from 2026-10-01 to 2026-10-14. It has not recurred since, for a reason I did not find.

Change	Why
The Milo bundle v0.32.5 to v0.36.5, by digest	v0.36.5 carries milo-os/milo#838, and it is the release production runs.
The Milo image digest to v0.36.5's index	The manifests and the binary stay on one release.

• The composed Milo deployment renders the same at both releases, except for the image digest.
• On kind, Milo v0.32.5 serves 13 identity definitions named by Go path and 13 references to them that kubectl's v2 parser cannot resolve; v0.36.5 serves none of either. On v0.36.5 the bring-up passed three times out of three. The suite passed twice; the third run failed one test, network-ipv6-prefix, which asserts on a prefix before it is set and fails the same way on v0.32.5.

Test plan

• E2E Tests and Federated E2E pass on this PR