Agenda

Antitrust Policy

• Action Items Review

• Proposal to merge SIG-Automation and Team Platform meetings

• Discussion on: https://github.com/nephio-project/nephio/issues/615 @James McDermott

• Built in function runner

• Review of other PRs on Porch

• What is the scope of Team Platform

Minutes

Merge SIG-Automation and Team-Platform

• We have separated and merged a number of times.

• We could spin out separate one-off meetings to deal with specific topics.

• We should keep the slot and we can use it for extra ad-hoc meetings.

• Decision: Merge the meetings and keep the slot for ad-hoc meetings.

Readiness Gates in Porch:

• Creating a package revision with a readiness gate set doesn’t work but it should, this is a bug

  • Create a new task similar to “clone” where you can set the readiness gate.

• Should we support a list of conditions on PRs that the Porch server checks before allowing a package to be proposed?

  • Could we repurpose some of the implementation in the Nephio operators? The Nephio implementation might be useful.

• R4:

  • Wire in the readiness gate and conditions into the “create” flow

  • Set the readiness gate to true on the server at the end of a pipeline run

  • Implement block of “propose” if the readiness gate is true in the server side

  • Testing etc.

• R5: Consider more sophisticated conditions

Built In Function Runner:

• Quick overview: There are three function runners in Porch:

  • Built-in function runner that imports the go code for the functions into the Porch server, this is the kpt functions are compiled in (Very fast and simple)

  • The executable function runner calls a binary that is already in the pod, so it runs the kpt functions binaries directly in the POD capturing sysin and sysout, the packages are piped into the exec call using sysin and the result is piped out. (Fast and fairly simple)

  • The function runner uses grpc communication to a special kpt-function-runner pod (Slower and complex)

• The Porch server uses the built-in function runner for some specific kpt functions

• Adding the executable function runner could be a flexible way of adding custom kpt functions

Workload Identity

• Please review

  • https://github.com/nephio-project/nephio/pull/809

  • https://github.com/nephio-project/catalog/pull/84

Action items