<p>I'm running Kubernetes in a GKE cluster and need to run a DB migration script on every deploy. For staging this is easy: we have a permanent, separate MySQL service with its own volume. For production however we make use of GCE SQL, resulting in the job having two containers - one more for the migration, and the other for Cloud Proxy.</p>

<p>Because of this new container, the job always shows as 1 active when running <code>kubectl describe jobs/migration</code> and I'm at a complete loss. I have tried re-ordering the containers to see if it checks one by default but that made no difference and I cannot see a way to either a) kill a container or b) check the status of just one container inside the Job.</p>

<p>Any ideas? </p>

<p>I know it's a year too late, but best practice would be to run single cloudsql proxy service for all app's purposes, and then configure DB access in app's image to use this service as a DB hostname.</p>

<p>This way you will not require putting cloudsql proxy container into every pod which uses DB.</p>
