Unicorn container initialization should be placed into initContainer
Currently, the unicorn
chart contains all application startup logic in the primary container, under scripts/process-wrapper
.
- Workhorse (quick)
- Call into Rails to turn off authorized keys file (currently only can be disabled from UI / rails)
- Spawn unicorn proper
The two Rails processes being back to back end up taking far too much time, and health checks fail, causing a restart of the pod and essentially looping for unknown amounts of time.
We should move the call to disable authorized key file generation to an initContainer
. My suggestion is to move the call to Rails into separate script, and supply an alternate exec
to the initContainer
definition, so we will only attempt to start the Pod
after the settings have been confirmed in place.
Edited by Jason Plum