#resource-limits

Portainer Swarm node labels and CPU limits for a low-traffic stack: which constraint actually controls placement?

I'm consolidating a low-traffic internal stack onto cheaper nodes in a Docker Swarm managed through Portainer. The plan is to label two small nodes (for example tier=low ) and use placement constraints plus CPU/memory limits in the stack definition so these services never land on the larger nodes and never consume more than a fixed share of resources. What I