Community meeting 2026-05-20 #4530

ciaranjohnston · 2026-05-20T13:15:25Z

ciaranjohnston
May 20, 2026
Maintainer

Attendance

Ahmed Ishaku Samaila
@liamfallon
@ciaranjohnston
@aravindtga
@mozesl-nokia
James McDermott
@efiacor
Rendre Grayling
@Jaisheesh-2006
Catalin Stratulat

If Ive missed you from here add your GitHub handle to the notes of the meeting notes

SDK strategy - Starlark support

@efiacor is working on better documentation and use the SDK in all the functions
Starlark
- All it needs is a reorganization of the documentation (Create an issue about this @CsatariGergely ). Collect all relevant information to https://catalog.kpt.dev/starlark/v0.5/#starlark-language
2026-05-20: there are two PRs up on this, one on the docs and one on the features, these will be handled on the technical meeting

Upgrade of Hugo/Docsy and change of UI "look and feel"

see Bump documentation go and docsy version #4511
New version of Docsy changes the look and feel a bit of the generated pages due to a bootstrap update in Docsy
Bump documentation go and docsy version #4511 implements the current look and feel of the pages
Let's use the default bootstrap styles
@aravindtga will update Bump documentation go and docsy version #4511 to remove the css changes.
Same goes for KRM Functions Catalog
2026-05-20: done, and waiting for review

Porch into kpt

Nephio SIG Architecture team discussed that Porch should be moved to under kpt governance
Nephio TSC have agreed this is the best approach and ratified the move on 2026-04-23
@liamfallon will create an issue about this in both the Porch and kpt side
2026-04-08: The issue in Nephio has been created here
2026-04-22: EPIC: Move the Nephio Porch repo to the kptdev CNCF project #4495 created.
We need to raise a ticket with LF to move porch repo to kptdev project - this will be a big bang so needs to be planned - release URLs will change as will repo urls - make a last release under Nephio before making the migration
2026-05-06: we did a release of 1.5.9 to Nephio, so we should raise a ticket with Casey Cain - @liamfallon will kick this off
2026-05-13: We have https://github.com/kptdev/porch ! Porch has been moved to the kpt organisation
- Change references to Nephio to kptdev porch#981 finalizes the needed changes
- If you have a pr in Porch rebase after Change references to Nephio to kptdev porch#981 has been merged!
- Todo
  - Change the usage of the Nephio Catalog repo
  - Remove Easy CLA (@CsatariGergely will do)
  - Move documentation to the kpt look and feel
  - Render the Porch documentation in a kpt space
  - Rename the Backstage plugin in kpt (@CsatariGergely )
  - Move the Porch Backstage plugins to kpt (@liamfallon )
2026-05-20: backstage plugin is moved, upgraded to latest version of backstage so CVEs are fixed. GUI will start, but beyond that has not been tested
Still TODO:
- Nephio catalog - need to rename porch_blueprint.tar.gz to porch-kpt-package.tar.gz, and update docs to point at that
- Remove Easy CLA (@CsatariGergely will do) - off porch but probably still on the backstage plugins
- Documentation to the kpt look and feel - there is already an issue
- Render the Porch documentation in a kpt space
- Need a new sonarcloud project: Move relevant repo to new Sonarcloud project #4528 - @ciaranjohnston to find out how this works in CNCF

Backlog handling

single or multiple backlogs?
Option 1: keep porch and kpt separate until they are triaged to a reasonable size, then merge
Option 2: keep porch and kpt and sdk and functions as 4 separate backlogs, and create a project to give a single pane of glass
Proposal to determine if option 2 is viable: create a project for option 1 while we have separate backlogs and use that as our "SPOG" during the triaging - then we decide if it is better than merging
2026-05-13: @CsatariGergely will create a project.
2026-05-20: no progress, still working with option 2

kpt-backstage-plugin

Should we support it?
If we do, should we move it back to kpt?
The current repo in kptdev is archived: https://github.com/kptdev/kpt-backstage-plugins
The Nephio version of the repo is here: https://github.com/nephio-project/kpt-backstage-plugins and has seen updates recently
Need to unarchive the kpt repo, move the updated content from the Nephio repo, then archive nephio repo with a message similar to the one we currently have in the kpt repo
@ciaranjohnston to create and issue and do the (un)archiving with @efiacor support for the porting
2026-05-06: no progress, wait until we move the porch repo
2026-05-20: completed move back to the kpt project

dedicated kpt/porch APIs repo

Circular dependency between sdk and kpt
How should we manage it?
@efiacor has a temporary patch - Break circ dependency with kpt krm-functions-sdk#751, we should move to this once the porch repo is moved
supports the move to v1
@ciaranjohnston and @efiacor to coordinate on creating a new repo
2026-05-06: no update. needs to be a new issue
2026-05-13:
- Create the issue under Stabilize kpt API to version 1 #4450 (@liamfallon )
- Create a new repo kpt-api with Apache License 2.0 (@ciaranjohnston ) -> Done (https://github.com/kptdev/kpt-api)
2026-05-20: two options - one is to use a separate repo for the api, the other is to keep it in the central kpt repo but make it a separate go module
- Consensus seems to be to keep in the kpt repo as a separate go module - we can revisit if this proves problematic

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.
2026-04-08: No progress
2026-04-15: @ciaranjohnston will finalize the text this week and send it for review. We might be able to send it to CNCF next week.
2026-04-22: @ciaranjohnston created a final version and shared on Blog post on kpt for CNCF website #4370 . Please review by Friday afternoon. Provide comments on Slack or to the discussion.
2026-04-29: @ciaranjohnston will submit to CNCF with addition of porch mention and a couple of nice diagrams / pictures
2026-05-06: finishing diagrams ...
2026-05-13: Diagram looks great! Last step is to go through on publishing.
2026-05-20: will be done this week

kpt beta.63

Will contain the content of v1.0.0-beta.62.1
Needs to contain security: upgrade go version to 1.25.9 to fix CVE-2026-27143 #4474 and chore: update kyaml/kustomize API versions to current versions #4480
kpt, krm-functions-catalog, krm-functions-sdk, Porch needs to have the same fix as security: upgrade go version to 1.25.9 to fix CVE-2026-27143 #4474
@aravindtga will work on this
2026-05-06: no update
2026-05-13:
- We are ready to cut a release in kpt
- There is a new pr for go version update (Upgrade Go version to 1.26.3 #4519), let's take this pr in this release
2026-05-20: need to take the latest version of go, comment made on the PR as it was only updated on one of them. @liamfallon to move on

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
- 2026-04-15: @liamfallon checked this and the only type is the conditions. @liamfallon started to work on this. We need ot have Go version for the two krm functions used in the tests to avoid architectural miscompatibility.
Update the documentation
The SDK and the function catalog have their separate versions
kpt --version should also provide the right version on all architectures
- There is this pr and an other pr. These contain some additional changes which are not needed. We should use the same way as it is implemented in Porch.
@liamfallon will create an issue to follow up on the version 1.0.0 work
2026-04-08: no progress
2026-04-22: @liamfallon created the issue for this (EPIC: Release kpt version 1.0.0 #4491)
- Planned around mid June
2026-04-29: will not get worked on directly for a couple of weeks - can wait until the new API repo is created, for consistency
2026-05-06: no update, @SurbhiAgarwal1 volunteered to write go versions of the 'no-op' and 'drop-comments'
2026-05-13: API repo is done, no progress on other fronts
2026-05-20: tracking under EPIC: Release kpt version 1.0.0 #4491, we can check weekly on status

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 discussion about the topic.
2026-04-08: No progress
2026-04-15: @efiacor did some housekeeping. There is a discussion for this: Pipeline and function execution considerations #4483

2026-04-22: Waiting for the v1.0.0 work to be done
2026-04-29 - 2025-05-20: still waiting ...

Developer guide

We should have a developers guide for the KRM functions
@CsatariGergely to create an issue
2026-04-29: we need better support given that people will still need to write their own functions - our support is non-existent. Starlark is very powerful but needs a deep understanding - we need a discussion on the SDK strategy. @efiacor has started looking at a list of issues around this
2026-05-06: ties into the SDK discussion - need to look at old PRs in that discussion
2026-05-13: @CsatariGergely will check for the old PR
2026-05-20: no update

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 (EPIC: Refactor the kpt code following the port of improvements from Porch #4378)
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
2026-04-08 - 2026-05-13: No progress
2026-05-20: @liamfallon and @mozesl-nokia to take as discussion next week

docs versioning

Use the same approach as with Nephio / Porch
2026-04-08 - 2025-05-20: No progress

Docs reorg

Remove the book structure - @CsatariGergely
2026-04-08 - 2026-05-20: No progress

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 Docs: 1.2 Quickstart: Show kubeconform catching some issues #1855
2026-05-06: Got to Design and implementation of "built-in" functions #1905
2026-05-13: Next one is kpt fn should show progress when downloading an image #1948 on Page 13
2026-05-20: Next one is Parallelize image pulling before running the pipeline #2026 on Page 13

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Community meeting 2026-05-20 #4530

Uh oh!

{{title}}

Uh oh!

Replies: 0 comments

Select a reply

Uh oh!

Community meeting 2026-05-20 #4530

Uh oh!

ciaranjohnston May 20, 2026 Maintainer

SDK strategy - Starlark support

Upgrade of Hugo/Docsy and change of UI "look and feel"

Porch into kpt

Backlog handling

kpt-backstage-plugin

dedicated kpt/porch APIs repo

CNCF Blogpost about kpt

kpt beta.63

kpt to v1.0.0

Mutation pipelines

Developer guide

Clean up the kpt repo

docs versioning

Docs reorg

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

Replies: 0 comments

ciaranjohnston
May 20, 2026
Maintainer