Skip to content
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

Merged
merged 2 commits into from
Nov 11, 2020

Conversation

Bobgy
Copy link
Contributor

@Bobgy Bobgy commented Nov 9, 2020

Which issue is resolved by this Pull Request:
Resolves kubeflow/metadata#250

Checklist:

  • Unit tests have been rebuilt:
    1. cd manifests/tests
    2. make generate-changed-only
    3. make test

@Bobgy
Copy link
Contributor Author

Bobgy commented Nov 9, 2020

/assign @PatrickXYS @Jeffwan @jlewi

@k8s-ci-robot
Copy link
Contributor

@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.
For more information please see the contributor guide

In response to this:

/assign @PatrickXYS @Jeffwan @jlewi

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.

@PatrickXYS
Copy link
Member

/test kubeflow-manifests-presubmit-e2e

@k8s-ci-robot
Copy link
Contributor

@PatrickXYS: No presubmit jobs available for kubeflow/manifests@master

In response to this:

/test kubeflow-manifests-presubmit-e2e

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
Copy link
Member

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.?

Copy link
Contributor Author

@Bobgy Bobgy Nov 9, 2020

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?

@Jeffwan @zhenghuiwang

Copy link
Member

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

Copy link
Contributor Author

@Bobgy Bobgy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reply

@PatrickXYS
Copy link
Member

The reason that E2E tests failed is

https://github.com/kubeflow/kfctl/blob/master/py/kubeflow/kfctl/testing/pytests/kf_is_ready_test.py#L86-L98

def test_metadata_is_ready(record_xml_attribute, namespace, cluster_name):
    deployment_names = [
        "metadata-deployment",
        "metadata-grpc-deployment",
        "metadata-db",
        "metadata-ui",
        "metadata-envoy-deployment",
        "metadata-writer",
    ]
    check_deployments_ready(record_xml_attribute, namespace,
                            "test_metadata_is_ready", deployment_names,
                            cluster_name)

Since this PR deleted metadata-ui, which breaks E2E tests, should send a PR to change E2E as well

@PatrickXYS
Copy link
Member

/retest

@@ -43,13 +38,6 @@ vars:
version: v1
fieldref:
fieldpath: data.uiClusterDomain
- name: metadata-service
Copy link
Member

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

@Jeffwan
Copy link
Member

Jeffwan commented Nov 11, 2020

/lgtm

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Jeffwan
Copy link
Member

Jeffwan commented Nov 11, 2020

Thanks @Bobgy driving the work

@k8s-ci-robot k8s-ci-robot merged commit 81a22d5 into kubeflow:master Nov 11, 2020
@PatrickXYS
Copy link
Member

@Bobgy Will this change go into v1.2-branch? If so, we may need cherry-pick this PR as well kubeflow/kfctl#440

@Bobgy Bobgy deleted the rm_metadata_ui branch November 11, 2020 22:59
@Bobgy
Copy link
Contributor Author

Bobgy commented Nov 11, 2020

Yes, I'll cherry pick it

@PatrickXYS
Copy link
Member

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

Bobgy added a commit to Bobgy/manifests that referenced this pull request Nov 12, 2020
* feat: remove outdated metadata UI manifests

* update again and snapshots
k8s-ci-robot pushed a commit that referenced this pull request Nov 12, 2020
* feat: remove outdated metadata UI manifests

* update again and snapshots
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Get Rid Of the Standalone Metadata UI
4 participants