-
Notifications
You must be signed in to change notification settings - Fork 822
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
feat: remove outdated metadata UI manifests #1619
Conversation
/assign @PatrickXYS @Jeffwan @jlewi |
@Bobgy: GitHub didn't allow me to assign the following users: jlewi. Note that only kubeflow members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
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/test-infra repository. |
/test kubeflow-manifests-presubmit-e2e |
@PatrickXYS: No presubmit jobs available for kubeflow/manifests@master In response to this:
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/test-infra repository. |
@@ -43,13 +38,6 @@ vars: | |||
version: v1 | |||
fieldref: | |||
fieldpath: data.uiClusterDomain | |||
- name: metadata-service |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is for metadata-service
not ui-service
.?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The obj reference targets UI service, and I removed its usage.
Do we still need to keep metadata server?
If yes, how do people access it? And how do people access it before? Was the UI service a proxy to the server?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We discuss this in another thread. I think we all agree to remove this. kubeflow/metadata#250
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reply
The reason that E2E tests failed is
Since this PR deleted |
/retest |
@@ -43,13 +38,6 @@ vars: | |||
version: v1 | |||
fieldref: | |||
fieldpath: data.uiClusterDomain | |||
- name: metadata-service |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We discuss this in another thread. I think we all agree to remove this. kubeflow/metadata#250
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Bobgy, Jeffwan 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 |
Thanks @Bobgy driving the work |
@Bobgy Will this change go into v1.2-branch? If so, we may need cherry-pick this PR as well kubeflow/kfctl#440 |
Yes, I'll cherry pick it |
For this PR kubeflow/kfctl#440, @pvaneck helped cherry-pick in this PR kubeflow/kfctl#441 So you should be good to only pick current PR #1619 |
* feat: remove outdated metadata UI manifests * update again and snapshots
Which issue is resolved by this Pull Request:
Resolves kubeflow/metadata#250
Checklist:
cd manifests/tests
make generate-changed-only
make test