rcscheduler does not recover from ungraceful shutdown

[colhom]

If a cluster is shut down ungracefully and is started again, the khealth controller's rcscheduler container comes back in an irrecoverable state. The health endpoint will forever report

init error: replicationControllers "khealth-rcscheduler" already exists

We should probably have rscheduler attempt to tear down any existing khealth-rcscheduler pods/rc/services before starting the init loop.