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
Is your feature request related to a problem? Please describe
The KFP Operator optionally adds a Pusher component to pipelines during compilation, if one doesn't already exist. The problem with this is that the Pusher is TFX specific, which means:
It won't make sense if we start supporting other frameworks in the future
It forces us to keep TFX (which is quite large) as a dependency in the KFP Operator codebase
As a bonus, it'll also simplify the Python compiler code :)
Describe the solution you'd like
Quite simple: remove the functionality that adds a Pusher component to TFX pipelines.
The text was updated successfully, but these errors were encountered:
alexgeorgousis
changed the title
Don't add Pusher component to pipelines
Don't extend pipelines with Pusher component
Jan 16, 2025
Is your feature request related to a problem? Please describe
The KFP Operator optionally adds a Pusher component to pipelines during compilation, if one doesn't already exist. The problem with this is that the Pusher is TFX specific, which means:
As a bonus, it'll also simplify the Python compiler code :)
Describe the solution you'd like
Quite simple: remove the functionality that adds a Pusher component to TFX pipelines.
The text was updated successfully, but these errors were encountered: