Feature summary (what you would like to be able to do and where):
I would like the webservice restart command (on the kubernetes backend) to issue the equivalent of a kubectl rollout restart deployment $TOOL_NAME command, instead of killing the pod as it currently does and then waiting for Kubernetes to recreate it.

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
By default, I believe this would not make any difference. However, for tools that configure liveness, readiness or startup probes (e.g. by adding them to the webservice-created deployment with kubectl patch), this would enable a restart with no downtime, since Kubernetes would wait until the new container is ready before sending traffic to it and deleting the old pod.

Benefits (why should this be implemented?):
Maintainers of tools that have defined a startup probe could then continue to use the standard webservice restart command, with the benefit of eliminating downtime, instead of having to remember to run the separate kubectl rollout restart deployment $TOOL_NAME command.