We're able to correctly unpause containers of services that are reached by an ingress session (including their dependencies).
For backend-trigger-involved services, their containers are not-pausable by default since they need to independently reach each other without any user intervention.
We're missing to cover service that for any reason need to connect to an external IP (egress session).
For this reason we should add an optional parameter in the service configuration to tell whether the container for a Docker-based service are pausable or not
We're able to correctly unpause containers of services that are reached by an ingress session (including their dependencies).
For backend-trigger-involved services, their containers are not-pausable by default since they need to independently reach each other without any user intervention.
We're missing to cover service that for any reason need to connect to an external IP (egress session).
For this reason we should add an optional parameter in the service configuration to tell whether the container for a Docker-based service are pausable or not