Provider Controller (Step 5)

[grahamia]

Overview

Now that we have simplified the components down which are involved in the feedback loop of run completion we can implement the controller within the KFP-Operator which will reconcile on the provider custom resources, i.e. #329. The beauty of being down to one component in the provider layer is that we have no need for managing resources together, i.e. we have no need for helm therefore the controller can apply the resource directly. The deployment should be marked as a sub resource of the provider resource, and handle create/update/delete/out-of-sync events.

Technical Details

• implement new controller, event processor deployment managed by controller
• on implementing the controller the permissions should be added to the roles.yaml permissions so the temporary manager-providers-viewer-rolebinding cluster role binding can be removed
• remove provider helm chart
• update the documentation
• status updates to the provider resource will have to be added at this point

Current Architecture

After Architecture

Acceptance Criteria

• on applying a new provider custom resource, the provider service deployment resource is created
• on updating the existing provider custom resource, then the provider service deployment is updated
• on deleting the provider customer resource, then the provider service deployment is removed
• when the provider service deployment is updated by something other than the provider controller, re-sync the deployment to match the provider resource
• when the provider service deployment is deleted, a new provider service deployment is created
• the provider service deployment must have a unique name (similar to how Deployments create pods with unique names)