Pausing Orchestration does not stop pods

[naisanza]

When you stop Orchestration, it does not stop the pods. The pods are still shown as running

[vincent]

Where I Pause the workload,the container still work

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).

[naisanza]

Oh I see, I was used to 1.6 stopping all Pods when the Service was stopped.