The problem is caused by the DynamicResources scheduler plugin not being automatically enabled when the feature flag is turned on. This makes DRA plugins run without issues (the right APIs are available), but do nothing.

Currently, KSO has three profiles: HighNodeUtilization, LowNodeUtilization and NoScoring. All three operator profiles take into account resource distribution. HighNodeUtilization focuses on locating as many pods possible around as few nodes possible, LowNodeUtilization focuses on locating pods as much evenly as possible across all nodes. NoScoring focuses on locating pods among all feasible nodes ignoring scoring. Given DRA extends the portfolio of resources to be taken account when scheduling support for DRA can be seen as a customization of already existing profiles. Either enable or disable DRA. In addition, DRA feature can be properly used only when vendor resource kubelet plugins are installed. For that a user is asked to explicitly enable DRA when all required kubelet plugins are on.