Very few people create pods directly - the docs say "replication controller" but should really say "pods created directly cannot be automatically evacuated". All other pods (managed by Deployments, Replication controllers, Daemon sets, Jobs, scheduled jobs, Builds, Pet Sets, etc) can.
Evacuation means "deletion of the pod". The pods are not moved. So someone has to be responsible for creating the pod again somewhere else. On Thu, Feb 4, 2016 at 11:09 AM, Hugo Rosnet <[email protected]> wrote: > Hi, > > I was reading the evacuate documentation > https://docs.openshift.com/enterprise/3.1/admin_guide/manage_nodes.html#evacuating-pods-on-nodes > > As stated it seems that "Only pods backed by a replication controller can be > evacuated", I looked around but couldn't find the answer to: > -Did the replication controller become included by default in pods creation? > > So that they are all able to be evacuated? > > Many thanks, > > Regards, > > -- > Hugo ROSNET > Technical Cloud Consultant > > RedHat > +33(0)141918251 | Copenhagen > > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
