<p>A new GKE cluster created at v1.1.1 and using latest kubectl (from gcloud components update) when deleting resources (say a pod) sometimes kubectl get pods in a 'Terminating' state and other times they delete (are removed from kubectl get pods output) right away.</p>

<pre><code>NAME                         READY     STATUS        RESTARTS   AGE
cassandra                    1/1       Terminating   0          44s
</code></pre>

<p>Is this new behavior of kubectl?  I don't recall it doing this at my prior levels.</p>

<p>Yes, it is new behavior in <a href="https://github.com/kubernetes/kubernetes/releases/tag/v1.1.1" rel="nofollow noreferrer">v1.1.1</a>. PR <a href="https://stackoverflow.com/questions/33836696/gke-1-1-1-and-kubectl-delete-resource-terminating">#9165</a> added graceful deletion of pods, which causes them to appear in the "Terminating" state for a short amount of time. Issue <a href="https://github.com/kubernetes/kubernetes/issues/1535" rel="nofollow noreferrer">#1535</a> has some more background discussion.</p>
