Community Meeting 2026-01-28

[CsatariGergely]

Attendance

• @liamfallon
• @CsatariGergely
• @mozesl-nokia
• @ciaranjohnston
• @efiacor
• @aravindtga

Topics and action items

Matters arising

• CVE from Google resulted in a new release of kpt - the process went quite smoothly and was turned around in a day
• Similar activity carried out in Porch
• Need to consider the backstage client plugins in the Porch UI repo

KubeCon EU 2026

• Liam and Isti were accepted to the Cloud Native Telco Day

Let's do the booth again

• A: @CsatariGergely to check with CNCF when can we subscribe for a booth.
• Would be nice to have more volunteers for the booth duty
• arrange an developer session as well - during maintainers summit or during one or more of the lunch sessions

KubeCon EU 2026 f2f developer meetings

Proposed topics

• We need to study mutation pipelines. Can we move the Porch mutation pipelines to kpt?
• Clean up the kpt repo

Actions from the Nephio dev event (#4254)

Enhancements

• Fix kpt live apply default values -> @kispaljr
  • Create an issue for this
  • Default values for resource id and resource name are random hashes. The hash needs to be saved to later have a deployment
  • we should use the name of the kpt package or mandate the resource id clp
  • 2025-11-19: issue still to be created
  • 2026-01-14: issue still to be created
  • 2026-01-21: issue still to be created. @CsatariGergely to check the status with @kispaljr
  • 2026-01-28: waiting a response
• We need to study mutation pipelines
  • Can we move the Porch mutation pipelines to kpt?
  • In the Porch repo there is a kpt folder which needs to move as well
  • kptfile structure has Slight differences in Kptfile upstream formatting with kpt pkg get and kpt alpha rpkg clone nephio-project/nephio#631
    • We could generate API documentation from go structs
  • 2025-10-29: need to kick off a workshop - @liamfallon to call for after Kubecon to triage
  • 2025-11-19: it's after Kubecon now ... @liamfallon to consider next steps, take half of the meeting on 2025-12-03 to handle this
  • 2026-01-14: Mutation pipelines will be in kpt and Porch will reuse them. We should still study how to advance the mutation pipelines.
  • 2026-01-21: Let's allocate time to discuss this on a meeitng. A: @CsatariGergely to ask @kispaljr about his preference and organize the meeting. Let's check if we can discuss this on KubeCon.
  • 2026-01-28: pencil in for Kubecon
• We should stop using the wet/dry analogy from the docs. It is confusing for users -> @CsatariGergely to follow up
  • 2026-01-14: No progress yet
  • 2026-01-21: No progress yet. No issue yet. A: @CsatariGergely to create an issue for this.
  • 2026-01-28: Issue is here: Stop using the wet / dry analogy #4360 - this is a porch concept. Closed from kpt perspective - @efiacor will create a task on the docs epic in porch
• Clean up the kpt repo
  • Lets keep it here and target later
  • 2025-11-19: no movement yet
  • 2026-01-21: Maybe this is an other topic for the KubeCon meeting.

Rollouts

• There is a functionality in kpt called Rollouts. We should decide if we keep maintaining it in kpt or move this functionality to Porch
• The functionality is the same what Porch/Nephio already implements with Package Variant Sets and Package Variants
• 2026-01-21: Let's remove it. A: @liamfallon to create a pr to remove the Rollouts functionality
• 2026-01-28: @liamfallon still has the action

Render KRM Function Catalog and kpt.dev to the same domain

• 2025-10-29: in progress, few different solutions while maintaining the two separate domains are under discussion
• 2026-01-14: Almost done. The only missing thing is to remove the new window opening when the function catalog link is clicked -> Gergely
• 2026-01-21: No progress
• 2026-01-28: Open Function Catalog in the same tab #4362 - done

clean up and remove parts of the krm-functions-sdk - @kispaljr to create an issue

• Next step is to move the parts back from Porch which were moved and developed there
• 2025-10-29: @CsatariGergely to check status with @kispaljr
• 2025-11-19: same as the issue further up?
• 2026-01-14: @CsatariGergely to check status with @kispaljr
• 2026-01-21: @CsatariGergely still to check status with @kispaljr
• 2026-01-28: there is some progress - Sync additional changes from Porch krm-functions-sdk#747

Update contributor guide https://github.com/kptdev/kpt/blob/main/CONTRIBUTING.md with reference to putting company in copyright header - @CsatariGergely

• 2026-01-14: No progress
• 2026-01-21: No progress
• 2026-01-28: PR ready for review / approval

Close off remaining actions on cncf/sandbox#154 - all

• Transfer of the trademarks / contribution agreement
• 2025-11-19: looks like this is well under control based on Kubecon discussion between @CsatariGergely and Daniel Krook
• 2026-01-14: No update from Daniel. Gergely will ping Daniel.
• 2026-01-21: No update from Daniel. Gergely will ping Daniel.
• 2026-01-28: Still no update

Some repos still have master

• Migrate all repos to main from master #4325
• @efiacor and @CsatariGergely will work on this
• @efiacor switched the catalog to main
• @CsatariGergely will do https://github.com/kptdev/krm-functions-sdk
• 2028-01-28: no progress on krm-functions-sdk

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

• Kill issues obviously non replaceable or Porch related
• Prioritize new issues
• Did some triaging and got down to What RBAC permissions for live apply? Correct values for apiGroups and resources #4095
• 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

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

We need a project mission for kpt. This is needed for the project control session

• A: Gergely to reboot a discussion on Slack about this
• kpt mission is "Automate Kubernetes Configuration Editing"
• 2025-11-19: @CsatariGergely to bump the discussion back up
• 2026-01-14: @CsatariGergely to really bump the discussions. Let's define the mission in next weeks meeting.
• 2026-01-21: We did this and can be removed from the list.
• 2026-01-28: Issue created to update the mission - we need to contact the formation team, @CsatariGergely will do that

Logo

• Gergely will replace the old logo to the new in the REAMDE.md of kpt
• 2026-01-21: Logo not yet replaced
• 2026-01-28: still pending

Google Summer of Code

• Deadline is 2026-02-03
• We need to have a project and someone who would mentor the volunteers
• Project ideas
  • E-commerce example (We can all be mentors) @liamfallon and @ciaranjohnston will create issue about this
  • Adding kpt project idea cncf/mentoring#1661 - will update the PR with different potential goals - basic, robust, stretch

PRs to be reviewed

• Next week - close PRs we are unlikely to handle - 2023 and earlier