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

Re: Issues with logging and metrics on Origin 3.7

On Mon, Jan 8, 2018 at 12:04 PM, Tim Dudgeon wrote: > Ah, so that makes more sense. > > So can I define the persistence properties (e.g. using nfs) in the > inventory file, but specify 'openshift_metrics_install_metrics=false' and > then run the byo/config.yml playbook

cloud provider problems

I'm having problems setting up openstack as a cloud provider. In Ansible inventory file I have this, and other parameters defining the cloud_provider. openshift_cloudprovider_kind = openstack When this is present openshift fails to deploy, and I get this error on the nodes as reported by

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.