Technical Meeting 2026-05-20

[liamfallon]

Agenda

1. Action Items Review
2. Priority PRs

• Add DeepCopy generation to all API types #4527
• Update apply-setters, create-setters and ensure-name-substring krm-functions-catalog#1240

4. Move of Porch to kpt
5. Flaky e2e tests in Porch
6. Copilot pickiness
7. Github performance
8. PR Triage
9. Issue Triage
10. AOB

Attendance

• @liamfallon
• @ahmadu2305
• @zaadnsu
• @aravindtga
• @Catalin-Stratulat-Ericsson
• @efiacor
• @Jaisheesh-2006
• @JamesMcDermott
• @kushnaidu
• @mozesl-nokia
• @rendre-greyling

Minutes

### PackageRevisionResources Healing

• Check with stakeholders, is there any problem removing the healing?
• 2026-05-13: Waiting on response @liamfallon
• 2026-05-20: No problem changing this

Force Pushing to git

• Should we change the git force push flag to “true”? Check with stakeholders.
• 2026-05-13: Waiting on response @liamfallon
• 2026-05-20: comments from @nagygergo, @mozesl-nokia. @rendre-greyling, and @kushnaidu

Porch pulls the latest, does some local operations, and then pushes again. If the git repo has changed in the meantime this is a problem for Porch. However, if any non-porch related changes are in other parts of the repo then they could get corrupted. At the moment when it pushes, it tries to do a rebase if there are changes and retries the push. If push-draft-to-git is on and the push fails and you continue to propose, git can get corrupted. Force pushing the approved PR is the only way to clear this.

This may be easier to deal with in the CRD implementation because it will be an asynchronous operation. If there is an existing push-render going on, then the next one gets requeued.

We can investigate solutions that allow push-draft-to-git to work with "force-push off" in both 1.5 and in the CRD version. Currently "push-draft-to-git" doesn't work correctly if "force-push" is off. This seems to be a bug in 1.5.

Deprecation timeline for the Porch v1alpha1 API

Thought is to set deprecation on v1alpha1 at the beginning of Q3 2026 and remove v1alpha1 at the beginning of Q2 2027, check with stakeholders @kispaljr
2026-05-13: Waiting on response @liamfallon @mozesl-nokia
2026-05-20: Waiting on response @liamfallon @mozesl-nokia

#4517 Deepcopy

DeepCopy is only implemented on a few types. This PR allows annotation-driven kubebuilder generation of deepcopy functions.

This has implications on the SDK cleanup work. This should get prioritized review.
Also check the SDK PRs and see if there is alignment issues.

The PRs to consider are:
#4517
kptdev/krm-functions-sdk#752
kptdev/krm-functions-sdk#752

Cleanup on KRM funcitons #4529

Please review!

Move of Porch to kpt

• see community meeting minutes

Flaky e2e tests

• Some PRs have been merged on this
• PR up to fix the deployment issue Improve CI deploy reliability, move CR cache tests to nightly porch#1002
• Please jump in and try to fix issue if you see them

Copilot pickiness

• Can we tune or customize Copilot to be less picky while still not missing important checks?
• If someone is willing to customize copilot please feel free to raise an issue

## Github performance

• Should we consider an alternative to Github?
• There are no hard rules to use Github but it is the best supported platform
• Let's kick this to the community meeting next week as a topic.

PRs to be reviewed

(Meeting did not get to this agenda point)

Porch

• WIP: Create remove fetches porch#246: This PR is to be moved into an issue because the PR is too old to easily merge, but the function it implementes would be good to have @nagygergo
• Reduce code duplication across rpkg CLI commands porch#541: Needs rebase and update so that it handles the v1alpha2 changes that were recently merged. Once those actions are taken, the PR should be OK to merge subject to a final review.
  • 2026-05-13: Reviewed byt he technical meeting, comemnts added to PR
• porchctl improvements porch#554: On hold, PR 541 must be merged first
• WIP: Refactor Performance Tests and add Grafana, Pyroscope and Prometheus monitoring stack porch#561: Outstanding comments
• Add package resource file sizes to PackageRevision interface porch#954: Outstanding comments
• Add SubpackageDir to API to support clone and upgrade of independent subpackages in a PR porch#974: Ready for review
• Add documentation for FunctionConfig CRD and reconciler porch#976: Outstanding comments
• Add PrrSizeBytes to v1alpha2 PackageRevision status porch#977: Outstanding comments (v1alpha2 version of kpt fn sink should allow merge strategies #954)
• Remove hardcoded MetalLB IPs from local dev scripts and tests porch#978: Outstanding comments
• docs: add versioned docs build with tag-based snapshots porch#980: Ready for Review
• Change references to Nephio to kptdev porch#981: Ready for review

kpt

• Replace random generated "inventory ID" #4396 - Needs rebase, but ready for review
• Docs/wasm function support #4419 - Community must decide if we wish to document the WASM functionality and decide whether to merge this PR or not, add to agenda for the community meeting next week.
• fix(update): preserve Kptfile formatting during upgrades #4427
  • 2026-03-18: needs rebasing and some copilot comments to be resolved. This could be very problematic to resolve ... needs a careful review
• 2026-04-22: Comments still not addressed
• 2026-05-06: Coments are addressed, @Jaisheesh-2006 will present this PR at the kpt technical meeting next week.
• feat: add builtin runtime support #4430 - We should decide if we need the mutation pipeline rearchitect work to be done before this is merged.
• 2026--05-06: Unadressed comments on the PR, no updates on PR since last month
• Update kyaml and kustomize API versions in catalog functions #4432 - has unadressed comments, see # almost identical fix: improve path validation in Kptfile functionConfig #4470, no action
  • There are lots of non related changes in the PR, no action from the author. If not change from the author next week we should close them.
  • 2026-05-06: No updates from author
• Refactor update logic in pkg/lib/kptops (cleanup + structure improvements) (#4379) #4441 - DCO problem, very large PR
  • There are lots of non related changes in the PR, no action from the author. If not change from the author next week we should close them.
  • 2026-05-06: No response from the author to invitation to present the PR at the community meeting.
• Split/fn eval namespace #4444 - has unadressed comments
  • On hold for now
• test: Update fn render E2E tests to use :latest set-namespace #4445 - has unadressed comments
  • On hold for now
• Fix GitHub Actions conditional expression in go.yml #4446
  • There are lots of non related changes in the PR, no action from the author. If not change from the author next week we should close them.
  • 2026-05-06: No response by author to suggestion to start fresh
• fix: remove porch references from kpt docs (#4288) #4453 - Ready for review
  • There are lots of non related changes in the PR, no action from the author. If not change from the author next week we should close them.
• docs: Add comprehensive documentation for kpt v1.0.0 API stabilization #4466 Test failures and copilot comments to be handled
  • There are lots of non related changes in the PR, no action from the author. If not change from the author next week we should close them.
• feat: Stabilize ResourceGroup API to v1 with backward compatibility #4467 Ready for review
  • There are lots of non related changes in the PR, no action from the author. If not change from the author next week we should close them.
  • 2026-05-06: No response by author to comments
• build: Implement semantic versioning in build system #4468
  • There are lots of non related changes in the PR, no action from the author. If not change from the author next week we should close them.
  • 2026-05-06: No response by author to comments
• feat: Add CEL-based conditional function execution (#4388) #4469 - address Copilot comments, Tests are failing, new PR with rebase of feat: Add CEL-based conditional function execution (#4388) #4391
  • 2026-05-06: The work for the v1 API will clean up the tests tat are causing this PR to fail, we should put this on hold and merge it once the tests are fixed.
• fix: improve path validation in Kptfile functionConfig #4470: @mozesl-nokia will comment regarding the go.mod changes
  • There are lots of non related changes in the PR, no action from the author. If not change from the author next week we should close them.
  • 2026-05-06: No response by author to comments
• fix: Improve kpt version command output and add comprehensive tests #4479
  • There are lots of non related changes in the PR, no action from the author. If not change from the author next week we should close them.
  • 2026-05-06: No response by author to comments
• Proofreading chapter 2 #4487 - Needs to address Copilot comments
  • 2026-05-06: Outstanding comments
• : docs: Add comprehensive documentation for kpt v1.0.0 API stabilization #4499
  • 2026-05-06: No response yet to comment on aligning with the community direction
• fix(live): propagate caller ctx into ResourceGroup inventory ops #4501
  • 2026-05-06: Outstanding comments
• Validate function tag literals before execution #4503
  • 2026-05-06: Approved, just needs to have the conflicts resolved.
• feat: add 'cat' command for displaying package resources #4505
  • 2026-05-06: Outstanding comments
• Bump documentation go and docsy version #4511
  • 2026-05-06: Awaiting review from @CsatariGergely
• Improve FunctionConfig related validation errors #4512
  • 2026-05-06: Ready for review
• Move more code out of internal #4515
  • 2026-05-06: Ready for review

krm-functions-catalog

• feat: port generate-folders function from TS to Go krm-functions-catalog#1216
• Move delete-annos fn from contrib krm-functions-catalog#1231
• Guideance on copyright notices and AI agent attributions krm-functions-catalog#1233
• Update favicons to the new logo krm-functions-catalog#1237