Comment 1 for bug 1665270

+1 to the need for this. I think we should consider adding a cap as a config option.

This is an issue in testing and publishing bundles that are one-size-fits-all. For example, the openstack-base or openstack-on-lxd bundles may work great on 8c or 16c boxes, but require tuning down max workers for ~7 charm applications on machines with 48c so as not to OOM the hosts.

One alternative/additive view is that Juju should implement container resource limits. I agree that is needed for this and other reasons. However, that wouldn't give the max workers cap tunable that is desired here.