-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
refactor(deployment): separate metadata-writer and metadata-grpc folders #4071
Conversation
+1 to this PR. I plan to deprecate metadata-writer and cache-server someday after we support native MLMD. So does persistence-agent. /lgtm |
I wonder maybe the Metadata Writer belongs more to the backend, not the metadata directory. |
@Ark-kun good point! will adjust |
8d78b8a
to
abdfb5c
Compare
New changes are detected. LGTM label has been removed. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Bobgy, rmgogogo 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 |
/retest |
/test kubeflow-pipeline-frontend-test |
/retest |
abdfb5c
to
db028ad
Compare
New changes are detected. LGTM label has been removed. |
New changes are detected. LGTM label has been removed. |
/test all |
/retest |
/test kubeflow-pipeline-backend-test |
/test kubeflow-pipeline-upgrade-test |
/retest |
/retest |
…ers (#4071) * refactor(deployment): separate metadata-writer and metadata-grpc folders * fix release script
Description of your changes:
Separate metadata-writer and metadata-grpc folders, so that we can reuse metadata-writer easier in Kubeflow 1.1 manifest by referring to the
kustomize/base/metadata/metadata-writer
folder directly./cc @Ark-kun
Checklist:
The title for your pull request (PR) should follow our title convention. Learn more about the pull request title convention used in this repository.
PR titles examples:
fix(frontend): fixes empty page. Fixes #1234
Use
fix
to indicate that this PR fixes a bug.feat(backend): configurable service account. Fixes #1234, fixes #1235
Use
feat
to indicate that this PR adds a new feature.chore: set up changelog generation tools
Use
chore
to indicate that this PR makes some changes that users don't need to know.test: fix CI failure. Part of #1234
Use
part of
to indicate that a PR is working on an issue, but shouldn't close the issue when merged.Do you want this pull request (PR) cherry-picked into the current release branch?
If yes, use one of the following options:
cherrypick-approved
label to this PR. The release manager adds this PR to the release branch in a batch update.