vizier-db needs enhanced liveness/readiness checks

[pdmack]

vizier-db pod is shown as "Running" after deployment but it actually is not fully configured if there was a problem with the katib-mysql PV not being writable.

OpenShift 3.11

$ oc logs vizier-db-7b4475c695-7vwt9
2019-01-21T14:33:28.470292Z 27562 [Note] Access denied for user 'UNKNOWN_USER'@'localhost' (using password: YES)
2019-01-21T14:33:30.469526Z 27563 [Note] Access denied for user 'UNKNOWN_USER'@'localhost' (using password: YES)
2019-01-21T14:33:32.471171Z 27564 [Note] Access denied for user 'UNKNOWN_USER'@'localhost' (using password: YES)

[jlewi]

@johnugeorge @YujiOshima @richardsliu Any plans to fix this in time for 0.5? Or should we move it into 0.6?

[richardsliu]

Moving this out of 0.5.

[gaocegege]

MySQL liveness probe requires mysqladmin.

https://github.com/helm/charts/blob/master/stable/mysql/templates/deployment.yaml#L122

In our MySQL image, we missed mysqladmin

Ref docker-library/mysql#410

Thus it is hard to add a liveness probe. Going to replace the image with a new one with mysqladmin.

[gaocegege]

/assign