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

Event Processor (remove argo events from provider) (Step 4) #359

Open
grahamia opened this issue Aug 30, 2024 · 0 comments · May be fixed by #391
Open

Event Processor (remove argo events from provider) (Step 4) #359

grahamia opened this issue Aug 30, 2024 · 0 comments · May be fixed by #391
Assignees

Comments

@grahamia
Copy link
Contributor

grahamia commented Aug 30, 2024

Overview

To simplify the eventing process within the provider we can drop the event source server/eventsource/sensor complexity and have one simpler single deployment which carries out the same functionality. The beauty of this is that now there is no dependency on argo events within the provider.

Technical Details

In this step the deployment of the new component can stay within the provider helm chart, in future card the deployment will be made part of the controller itself with no need for provider helm anymore.

The DataWrapper in the KFP Operator webhook can be removed at this point as no argo events wrapping needed.

Current Architecture

image

After Architecture

image

Acceptance Criteria

Eventing feedback should function as currently with no change
Testing should be carried out to ensure that same retry logic on failure exists and at least once consistency is maintained.

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

Successfully merging a pull request may close this issue.

4 participants