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

Improve Third-Party Deployment Plugins Reliability and Compatibility #4318

Open
DimedS opened this issue Nov 11, 2024 · 1 comment
Open

Improve Third-Party Deployment Plugins Reliability and Compatibility #4318

DimedS opened this issue Nov 11, 2024 · 1 comment
Assignees
Milestone

Comments

@DimedS
Copy link
Contributor

DimedS commented Nov 11, 2024

Overview

Part of #4317. This issue focuses on addressing user challenges with Kedro's third-party connection plugins for deployment. We aim to ensure that these plugins remain reliable and compatible with the latest Kedro versions while offering a flexible approach to managing platform-specific features.

User Insights and Challenges

  • Kubeflow Plugin: Users are exploring ways to use the Kubeflow plugin for compiling and deploying Kedro pipelines but face issues with outdated functionality.
  • Databricks Integration: Some users prefer interacting with the Databricks API manually via Asset Bundles to achieve greater flexibility, rather than using the Kedro-Databricks plugin.
  • Argo Workflows: Translating Kedro pipelines into Argo Workflows manifests is a significant challenge.
  • SageMaker Plugin: The Kedro-SageMaker plugin was not used due to incompatibility with Kedro 0.19, limiting its application for certain projects.

Each connection plugin includes two key functionalities:

  • Converting Kedro pipelines for different platforms
  • Handling API interactions to upload and execute the converted pipelines

Goals

Ensure Long-Term Compatibility: Maintain and update third-party plugins regularly to align with the latest Kedro releases.

Possible Solutions

  • Split Plugin Functionality: Divide each plugin's functionality into two parts:
    • Pipeline Conversion: Kedro maintainers will support and maintain the part responsible for converting Kedro pipelines to various platforms.
    • API Interactions: The community will handle the API interaction component, responsible for uploading and running the converted pipelines on specific platforms.
  • Resource Optimization: By splitting responsibilities, Kedro maintainers can focus on the core functionality (pipeline conversion), saving resources while ensuring essential compatibility, and empowering the community to maintain API-specific integrations.
@DimedS DimedS added the Issue: Feature Request New feature or improvement to existing feature label Nov 11, 2024
@merelcht merelcht added this to the Deployment milestone Nov 11, 2024
@merelcht merelcht removed the Issue: Feature Request New feature or improvement to existing feature label Nov 11, 2024
@merelcht merelcht moved this to To Do in Kedro Framework Nov 11, 2024
@DimedS
Copy link
Contributor Author

DimedS commented Nov 18, 2024

Summarised the current state of deployment plugins, highlighting the node grouping functionality:

https://www.notion.so/mckinsey/1423043f5dcf80b7a6cdf21901ff55c2?v=7958cdee2674405b82de8dd318d9fa1f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

3 participants