I read your initial post again and I think I don't understand what the term "server pool" means. Could you clarify?
Without knowing anything about the software, the organisation building it and deployment target it's very hard to give you anything but generic advise. In my view the main benefit of containerised systems are that it isolates each app and allows you to make easily deployable units.
As an example: let's say you're running a webapp. You could have the software running on a couple of containers in your live environment and have something like HAProxy in front the containers. Now, when you want to upgrade you spin up new containers for new version, update HAProxy to gracefully redirect traffic to the new containers and as all users have been migrated you shut down the old containers. Found a showstopper bug with new version? Just do the same thing in reverse and spin up the older version containers and update your HAProxy (this naturally assumes there were no destructive changes to data store in between).
The containers also work well in the micro-services architecture where you have small services responsible for small tasks. Having these in containers allow you to flexibly change where the services are run (for example if you run out of capacity on a physical host). Deployments also become somewhat easier because the same container you run locally will also run in other environments (no more "someone forgot to install this and that dependency on that box").
I guess I could write an essay as an answer but in the end the decision whether the benefits outweigh the cost of getting the system running can only be made by someone who understands the actual software and the organisation around it.