Re: Pod persistence without replication controller

You could use a StatefulSet if you want a consistent hostname, it would also ensure that there is a always one running. On Wed, 10 Jan 2018 at 3:49 am, Feld, Michael (IMS) wrote: > Does anyone know why a standalone pod (without a replication controller) > sometimes persists

Pod persistence without replication controller

Does anyone know why a standalone pod (without a replication controller) sometimes persists through a host/node reboot, but not all times (not evacuating first)? We have a database pod that we cannot risk scaling, and want to ensure that it's always running.