Community meeting 2026-04-01

[CsatariGergely]

Attendance

• @mozesl-nokia
• @aravindtga
• @efiacor
• @liamfallon
• Timo
• Gergely
• Pushpit Saluja

Topics and action items

KubeCon EU 2026

• Project engagement survey
• Deadline Wednesday, 15 April.
• @CsatariGergely will post the quesitons to Slack for discussion

KubeCon EU 2026 f2f developer meetings - side meetings during main conference

• @ciaranjohnston @liamfallon @mozesl-nokia @CsatariGergely @kispaljr did attend
• Notes are here
• We even have a group photo!

GSoC

• Application deadline was yesterday
• 16 proposals received
• Let's have a mentor meeting to analyze the proposals @CsatariGergely will organize.
• Deadline is 21 April

Triaging of issues - in progress, start next week's meeting

• Kill issues obviously non replaceable or Porch related
• Prioritize new issues
• 2025-11-19: PRs were cleared down - the ones left were unknown or should be merged. Still need to triage issues - will do that next week's meeting
• 2026-02-04: Did some triaging - Avoid the use of external diff tools for the kpt pkg diff command #1808 is next to be done
• 2026-02-11: @liamfallon checked all the prs. There are new functions in the catalog, there is one documentation pr in kpt ([WIP] Function SDK guide #3367)
• 2026-02-18: Got to tree command should optionally (?) show whether a package is dependent or independent #1845

CNCF Blogpost about kpt

• We should do it!
• Content should be similar to the talk what we planned
• A: Gergely will start working on this with CNCF
• 2025-11-19: still TBD
• 2026-01-14: still no progress
• 2026-01-21: still no progress
• 2026-01-28: question asked at the maintainers circle channel on CNCF slack - still waiting for an answer - start writing this week by planning here: Blog post on kpt for CNCF website #4370
• 2026-02-04: no progress
• 2026-02-11: @ciaranjohnston proposed a skeleton. Let's use this skeleton as a basis.
• 2026-02-18: Fill this for CNCF to publish the blogpost: https://form.asana.com/?k=Ufi_ZE31X3EAKMTiplIEcA&d=9283783873717. @ciaranjohnston drafted most of the blogpost. See it here: Blog post on kpt for CNCF website #4370 (comment)
• 2026-02-25: We should have an articles section in the website. We did not submit the publication form yet.
• 2026-03-04: no progress
• 2026-03-11: No progress. Content looks great for @CsatariGergely
• 2026-04-01: @ciaranjohnston will finalize the text this week and send it for review. We might be able to send it to CNCF next week.

Update project logo in the control center - @CsatariGergely

• 2026-03-11: no progress

Contributing guides - @CsatariGergely

• Linting and AI comments should be either resolved or marked non relevant before humans will review the code
• Add to contribution guidelines and to the pr templates
  Proposal from @liamfallon for guidelines:

Process for Code reviews, before a “human” code review a PR:
* Must have all tests passing
* Must have all linting passing
* Must meet code quality criteria (coverage etc)
* Must have all automatically generated comments addressed (AI generated comments, SonarCloud comments, bot generated comments etc)
* Where possible, automatic comments should be resolved
* If it is not possible to resolve an automatic comment, please add a sub-comment indicating why the automated comment cannot be resolved or ask for help in resolving the comment
* Discussion on DCO - agreement that we should enforce this - exceptions should be requested from maintainers

• 2026-03-04: @liamfallon will work on the text in porch for a contributor guideline and then bring here
• 2026-03-11: no update
• 2026-04-01: kpt pr, krm-functions-catalog pr. There are more comments from Copilot what @CsatariGergely needs to fix. There is a pr to fix the e2e tests for the krm-functions-catalog. There are suggestions from @liamfallon to be considered.

Branch protection rules

• Set "comments to be resolved to true" -> @CsatariGergely
• 2026-03-11: @CsatariGergely needs to doublecheck is this is done
• 2026-03-21: Done

kpt beta.62

• @efiacor will check if we need to release the SDK before releasing kpt

kpt to v1.0.0

• There are some types copied from Kubernetes and kubctl. We should go back and use the upstream ones. These are in kpt and in Porch also
• Update the documentation
• The SDK and the function catalog have their separate versions
• kpt --version should also provide the right version on all architectures
• @liamfallon will create an issue to follow up on the version 1.0.0 work

Mutation pipelines

• For working on the pipeline we should not need Porch
• move the Porch mutation pipelines to kpt
  • Function execution environment
  • Render pipeline execution
  • The Porch multi executor should be moved to kpt
• 2026-04-01: Issue to follow up the whole activity: Rearchitect pipelines #4449. feat: add builtin runtime support #4430 touches a similar area. Let's pull all relevant pipeline related issues under Rearchitect pipelines #4449, @ciaranjohnston will create a dicussion about the topic\

We should use consistent naming for mutation pipelines and related concepts in the documentation

• @CsatariGergely and @kispaljr will work on this together with the Nokia tech writer team

kpt - Porch border

• organize a public go API in the kpt repo what is used by Porch
• We need an issue for this

Porch back to kpt governance

• Nephio SIG Architecture team discussed that Porch should be moved to under kpt governance
• Nephio TSC will discuss the topic on 9.4.2026
• After that we should decide if we take Porch in
• @liamfallon will create an issue about this in both the Porch and kpt side

Clean up the kpt repo

• Clean up the upgrade / update terminology
• Need to refactor / remove the "thirdparty" - refer to upstream or absorb
• update the internal utils/update directory
• versioning, 3-way merge needs to be brought into the kpt documentation
• remove kpt/docs - @CsatariGergely
• remove firebase references
• investigate healthcheck to see if it is needed
• refactor what was moved over from porch
• some of the stuff (all?) in internal can be moved out - are there internal APIs we want / need to protect?
• mdtogo - do we keep this or is it copied from somewhere else?
• should examples move to samples? These are used for running tests so maybe not
• investigate oci in the pkg directory
• kpt/pkg/printer needs investigating
• kpt/run needs investigating
• 2026-04-01: We need an epic type of issue with these topics as sub issues - @liamfallon or @mozesl-nokia

Refactor the kpt code following the port of improvements from Porch EPIC

• EPIC: Refactor the kpt code following the port of improvements from Porch #4378

docs versioning

• Use the same approach as with Nephio / Porch

Docs reorg

• Remove the book structure - @CsatariGergely

PRs to be reviewed

kpt

• Local tag lister for semantic version constraint matching #4458 - has Copilot comments
• fix: remove porch references from kpt docs (#4288) #4453 - It has lots of changes not related to the documentation, has the DCO issue
• Update CONTRIBUTING file with PR review rules #4452 - needs more work form @CsatariGergely
• Fix GitHub Actions conditional expression in go.yml #4446 - merged
• test: Update fn render E2E tests to use :latest set-namespace #4445 - has unadressed comments
• Split/fn eval namespace #4444
• Refactor update logic in pkg/lib/kptops (cleanup + structure improvements) (#4379) #4441
• Add basic e-commerce kpt example #4440
• Add RenderStatus to the Kptfile for per-function pipeline result tracking #4437 - @mozesl-nokia approved. @liamfallon will check.
• Update kyaml and kustomize API versions in catalog functions #4432 - has unadressed comments
• Simplify ImageResolveFunc #4431 - @liamfallon will check
• feat: add builtin runtime support #4430 - We should decide if we need the mutation pipeline rearchitect work to be done before this is merged.
• fix(update): preserve Kptfile formatting during upgrades #4427
  • 2025-03-18: needs rebasing and some copilot comments to be resolved. This could be very problematic to resolve ... needs a careful review
• test: Update set-namespace E2E tests to use :latest version #4420
• Docs/wasm function support #4419
• Replace random generated "inventory ID" #4396
• feat: Add CEL-based conditional function execution (#4388) #4391
  • 2025-03-18: both failing for the same reason, due to PR Replace gcr.io container image references with ghcr.io #4428 - which was changing WASM. @SurbhiAgarwal1 and @ciaranjohnston to rebase to see if this resolves it
  • 2026-04-01: ready for review. Ok for @nagygergo . @liamfallon @mozesl-nokia to review

We did not review these

• Fix #1407: Make 'kpt pkg get' use current directory when '.' is specified #4334
  • 2025-03-18: both failing for the same reason, due to PR Replace gcr.io container image references with ghcr.io #4428 - which was changing WASM. @SurbhiAgarwal1 and @ciaranjohnston to rebase to see if this resolves it

krm-functions-catalog

• Search and Replace: Validate against openAPI #1228
• the type KptFile doesn't work for ConfigSync parser #1227
• docs: update helm-template to helm-inflator #1226
• Search and Replace: Support advanced path expressions #1225
• [WIP] Updates with resource-merge strategy happens per-package #1220
• Add install-resource-group command in live command #1216