Our documentation does not mention anywhere that the Latency Profiles for workers do not support any custom Machine Config Pools. This is misleading for customers and engineers when the Latency Profile is not getting applied to the custom MCP but only to the default worker MCP. After talking with engineering team i ve been told that this is expected behavior but it is mentioned nowhere in the docs.

Not a specific version. All versions that support Latency profiles. Seems since v4.11

I will raise an RFE for this feature to be implemented in the future as it was requested by a customer.