Try to add a cmd line arg on 'connectTimeout ' to satisfy low performance storage.
/kind feature
When using some old storage, katib-mysql may init fail. when init kubeflow on some TCP net disk or glusterfs(with TCP).
the mysql.go init connectTimeout is set to 60 sec.
May add a arg on this timeout setting.
So user can set a longer time on init katib-mysql.
Love this feature? Give it a 👍 We prioritize the features with the most 👍
In my case , i think the katib-db-manager
will auto exit with in 60 sec, what erver the pod setting.
Thanks for requesting a new feature! @techwolf139 I would like to implement this after #1921 is merged.
Thanks @tenzen-y
/assign
cheers Is there some other hard coded timeout setting?