You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
I’m looking for the best way to create an initial database during the cluster setup. My current thought is to create a Kubernetes Job that connects to the database and runs the necessary SQL commands to create the database . However, I’m wondering if there’s a more efficient or declarative way to handle this.
For example, is it possible to include an initdb.sql file or some equivalent directly in the MySQLCluster spec? If so, how would that work, and would it be better than using a Job?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi
I’m looking for the best way to create an initial database during the cluster setup. My current thought is to create a Kubernetes Job that connects to the database and runs the necessary SQL commands to create the database . However, I’m wondering if there’s a more efficient or declarative way to handle this.
For example, is it possible to include an initdb.sql file or some equivalent directly in the MySQLCluster spec? If so, how would that work, and would it be better than using a Job?
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions