-
Notifications
You must be signed in to change notification settings - Fork 903
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metadata db in overlay #673
Conversation
use parameter files for db configuration
@xaniasd do you know why the tests failed? /assign @zhenghuiwang |
/retest |
@jlewi not really, haven't spent much time on understanding the CI part so it's a bit cryptic to me. Code (+tests) work on my machine though 😄 I'm running the tests again, hopefully it was just a glitch |
@jlewi it was a glitch indeed |
/lgtm Thanks @xaniasd ! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: zhenghuiwang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
similar to kubeflow#673, this allows users to create their own overlay to use external databases.
similar to kubeflow#673, this allows users to create their own overlay to use external databases.
similar to kubeflow#673, this allows users to create their own overlay to use external databases.
similar to kubeflow#673, this allows users to create their own overlay to use external databases.
similar to kubeflow#673, this allows users to create their own overlay to use external databases.
similar to kubeflow#673, this allows users to create their own overlay to use external databases.
similar to kubeflow#673, this allows users to create their own overlay to use external databases.
similar to kubeflow#673, this allows users to create their own overlay to use external databases.
similar to kubeflow#673, this allows users to create their own overlay to use external databases.
Which issue is resolved by this Pull Request:
Resolves kubeflow/metadata#171
Description of your changes:
With this PR the metadata-db is deployed as an overlay and not with the base layer. This allows deployments using an external (to Kubeflow) database server to avoid security risks and wasting resources. The default KfDef files are updated to use the overlay; use cases such as the one outlined here must remove the db overlay from KfDef and use a custom overlay to configure the metadata deployment.
Checklist:
cd manifests/tests
make generate
make test
This change is