When new cri-resmgr configuration is applied through cri-resmgr-agent, changes in AvailableResources, ReservedResources or AllocatorTopologyBalancing do not trigger realignment of workloads yet it should. As a consequence, workloads may continue to use CPUs that are not (anymore) available to cri-resmgr, for instance.