Where I Pause the workload,the container still work

I click the button “Pause Orchestration” or use the v3 api to pause the workload, and the workload’s state change to “Paused”.

But I find I still can visit the servcie in the docker container built by the “paused” workload .

Is there an way or bulid policy to stop the container where I pause the workload? Which has the same effect like docker commad “docker stop pid”


No; pausing stops the controller from deploying new revisions temporarily so you can make several changes in a row (e.g. adding multiple sidecars) without repeatedly redeploying the containers. Kubernetes does not have a concept of “stopped” pods. You can scale the workload down to 0 and back, but this is not quite the same (you won’t get the same pods back).

1 Like