[feature] Adding an option to skip database creation/migration logic

[lkaybob]

Feature Area

/area backend

What feature would you like to see?

Adding an environment variable option to allow skipping database migration logic, so that Pipelines backend applications run properly when db schema creation is handled by admin process (as ml-metadata allows).

What is the use case or pain point?

While KF Pipelines backend have database creation/migration logic included, it does not have an option to skip database migration. This makes application startup fails when DB user used by application does not have enough privilege to execute DDL statements.

Is there a workaround currently?

We've first created a SQL dump of database schema(mlpipeline, caches) of backend applications from freshly deployed Kubeflow cluster where we manage by ourselves, and executed the dump manually to production environment.

Since the applications still executes DDL statements regardless of existence of schemas, we have hard-forked the repository and disabled the DB migration logic by commenting out the relevant code so far.

• From apiserver: Database creation, Table creation, Updating indices
• From cache: Database creation, Table creation

(If possible, I would like to make a contribution of the feature.)

---

Love this idea? Give it a 👍.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[rimolive]

no stalebot, this is relevant.

[rimolive]

/assign @rimolive

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

[rimolive]

/reopen /lifecycle frozen

[google-oss-prow[bot]]

@rimolive: Reopened this issue.

In response to this:

/reopen /lifecycle frozen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.