You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 2020, Kirin had left the project, and the Kubeflow Pipelines community decided to deprecate Python based visualizations. issuePR
The recommendation became to use notebooks or the HTML output viewer to accomplish what you could have using the "Python based visualizations" feature.
Post deprecation, there was a lot of language left over in the output viewer documentation that described "Python based visualizations" as the "new" way to do visualizations. This was confusing. I've previously posted a PR to clean some of that up, but much lingers.
It's been 4 years since it was deprecated. It probably should have been removed when Kubeflow Pipelines 2.0 was released.
Let's remove it now.
The text was updated successfully, but these errors were encountered:
One thing I'm not sure how to do: how does Kubeflow / KFP handle cleaning up deprecated and deleted things? Should we include some kind of upgrade scripts of manifests that are capable of cleaning up Deployments, Roles / RBAC, SAs, etc.?
What feature would you like to see?
As far as I can tell, there are two primary categories of visualization in Kubeflow Pipelines:
Output viewer visualizations are the original visualizations that were included in Kubeflow Pipelines long ago.
In 2019, Kirin Patel introduced "Python based visualizations" to Kubeflow Pipelines (commits, blog post).
Note the introduction of the "visualization server".
In 2020, Kirin had left the project, and the Kubeflow Pipelines community decided to deprecate Python based visualizations.
issue PR
The recommendation became to use notebooks or the HTML output viewer to accomplish what you could have using the "Python based visualizations" feature.
Post deprecation, there was a lot of language left over in the output viewer documentation that described "Python based visualizations" as the "new" way to do visualizations. This was confusing. I've previously posted a PR to clean some of that up, but much lingers.
It's been 4 years since it was deprecated. It probably should have been removed when Kubeflow Pipelines 2.0 was released.
Let's remove it now.
The text was updated successfully, but these errors were encountered: