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
After Architecture
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.
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
After Architecture
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.