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

[feature] Remove deprecated components #10905

Open
2 tasks
AndersBennedsgaard opened this issue Jun 14, 2024 · 3 comments
Open
2 tasks

[feature] Remove deprecated components #10905

AndersBennedsgaard opened this issue Jun 14, 2024 · 3 comments

Comments

@AndersBennedsgaard
Copy link

AndersBennedsgaard commented Jun 14, 2024

Feature Area

/area backend

(there more be more areas I don't know of)

What feature would you like to see?

There are several components in this git repository that are no longer in use.
These include (original comment: #7725 (comment)):

(feel free to comment additional components that could be removed, and I will add them to the list)

If we want backwards compatibility, we could create separate Kustomize components for deprecated resources which are enabled by default, and disable them at some point in the future before completely removing them.
Additionally, in the profile controller, we could look for a V1_BACKWARDS_COMPATIBILITY environment variable to only conditionally deploy the visualization server and artifact UI.

What is the use case or pain point?

Installation of KFP using something like kubectl apply -k ./pipelines/manifests/kustomize/env/platform-agnostic-multi-user includes a lot of unnecessary resources, which just take up space and computational resources.
It is also hard to know which components are needed if you only run KFP v2.

Is there a workaround currently?

Continue as usual. Ignore the high resource usage from all the visualization servers and artifact UIs in all user namespaces.


Love this idea? Give it a 👍.

Copy link

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 github-actions bot added the lifecycle/stale The issue / pull request is stale, any activities remove this label. label Aug 14, 2024
@AndersBennedsgaard
Copy link
Author

Still relevant

@juliusvonkohout
Copy link
Member

Yes very relevant @rimolive
/lifecycle frozen

@google-oss-prow google-oss-prow bot added lifecycle/frozen and removed lifecycle/stale The issue / pull request is stale, any activities remove this label. labels Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants