Chris, I'm not sure how much more clear we can be. I mean, this is the warning, as you noted:
"Caution
Host aggregates should be used to separate pinned instances from unpinned instances as the latter will not respect the resourcing requirements of the former."
It is 100% clear to me that the operator should not mix non-NUMA-pinned instances with NUMA-pinned instances. This use case is for a "resource-constrained environment" which I presume means that the operator is, indeed, violating the very warning that was placed into the documentation for this specific reason.
Chris, I'm not sure how much more clear we can be. I mean, this is the warning, as you noted:
"Caution
Host aggregates should be used to separate pinned instances from unpinned instances as the latter will not respect the resourcing requirements of the former."
It is 100% clear to me that the operator should not mix non-NUMA-pinned instances with NUMA-pinned instances. This use case is for a "resource- constrained environment" which I presume means that the operator is, indeed, violating the very warning that was placed into the documentation for this specific reason.