During an upgrade process, a service may have 1 stopped container and 1 active container. Rancher-gen reads these properly, but our currently template doesn't handle stopped vs running containers properly and produces an Nginx config that doesn't route properly.
The solution may be to handle stopped vs running containers better.
During an upgrade process, a service may have 1 stopped container and 1 active container. Rancher-gen reads these properly, but our currently template doesn't handle
stoppedvsrunningcontainers properly and produces an Nginx config that doesn't route properly.The solution may be to handle
stoppedvsrunningcontainers better.