That is very helpful. So with that in mind, I was able to kubectl delete -f <myfile> and then recreate it with my updated yaml.
Thanks a bunch On Friday, June 17, 2016 at 12:57:16 PM UTC-4, Matthias Rampke wrote: > > > On Jun 17, 2016 15:30, "D Mitchell" <[email protected] <javascript:>> > wrote: > > > > > [root@paas1 routeone]# docker ps |grep dash > > fbf6fb0ac807 gcr.io/google_containers/pause:2.0 > "/pause" 50 minutes ago Up 50 > minutes > k8s_POD.3a1c00d7_kubernetes-dashboard-8ceoe_kube-system_24cc2e7d-3406-11e6-891d-005056b28e11_a41023d6 > > > > > > If I kill that, it'll restart immediately. I can't get rid of the > thing. > > You cannot remove a pod by way of Docker – Kubernetes will just detect > that the state of the node is not what it should be and rectifies that. > This is similar to trying to stop a systemd service by killing the service. > You basically *never* want to interact with Docker itself on the node. > > Instead, you need to use kubectl to delete the pod. Kubernetes will take > care of shutting down the containers. Then it will be replaced by the > replication controller. > > /MR > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
