Planned - Nephio: kpt function/mutation pipeline execution model

Short Description

Topic Overview

Today, kpt functions in Porch have two models:

1. A small number of kpt functions are compiled into Porch and run in the Porch server

2. Most kpt functions run in a separate container, which is started separately to the Porch server. Execution of a kpt function is invoked on the separate container over gRPC

Approach 1. suffers from the drawback of having to clone the kpt function code into Porch and separately manage/track its lifecycle with all the “clone and own” drawbacks.

Approach 2. whilst being very flexible suffers from the drawback of being very resource expensive as well as having very complex runtime interactions and being expensive to maintain, test, and support.

In this session we will explore a third approach, which will allow us to simplify the mechanisms for invocation and running kpt functions.

Session Type

Slides & Recording

Notes From Session (as appropriate)

Action Items (as appropriate)