Community meeting 2026-07-29

[CsatariGergely]

Attendance

• @aravindtga
• Oisin Johnston
• @efiacor
• @rendre-greyling
• @liamfallon

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

ONE Summit / Open Source Summit Japan

• We should work on proposals
• CfP Deadline 08.24
• We should put the demo talk and the "rejected" talk in for ONE Summit and Open Source Summit
• https://events.linuxfoundation.org/open-source-summit-japan/program/cfp/#overview
• https://events.linuxfoundation.org/open-networking-edge-summit-japan/program/cfp/

KubeCon NA 2026

• deadline for booths is up on next week
• @ciaranjohnston to apply for a booth slot
• deadline missed for submissions for talks
• 2026-07-22:
  • @ciaranjohnston submitted for a booth in the project pavilion
  • @liamfallon will be possible there
  • @CsatariGergely will be possibly not there
• 2026-07-29:
  • No updates from CNCF

Sylva WG6 Hackaton

• https://wg06-workloads-lcm-gitops-59a50a.gitlab.io/events/hackathon/
• 23rd-24th of November in Bern
• Do we want to propose a kpt topic?
  • Let's wait for @ciaranjohnston 's opinion
• 2026-07-29:
  • We did not submit a topic (yet)
  • Gergely will ask Ciaran on Slack about kpt/Ericsson participation

Architecture workshop

• We need some days together to come up with an architecture for the next 2-3 years.
• Let's try to do a face to face
• ~6 hours
• How about in Prague on Oct 5?
  • Part of the team will be there for Open Source Summit later the same week
  • Nokia has an office, maybe we can get a room.
• Topics
  • Parallel mutation pipelines
  • CRDs in Porch (should we keep the database for other than the resources?)
  • If you have more topic ideas add them as a comment here or propose them on Slack
  • Decouple function execution from pipeline step definition ([Proposal] Decouple Function Execution from Pipeline Step Definition #4647 )
• 2026-07-15: no progression
• 2026-22-07:
  • Gergely will ask Daniel if we can have a room
• 2026-07-29:
• Gergely asked Daniel and the answer is not no.
• The plan is to make the workshop free to attend

Github budgets for actions and CoPilot

• kpt runners are waiting for runners
• Copilot stopped auto reviewing new PRs
• We implemented a policy that Copilot will review only first commits and not all
• We were charged ~9 USD this month
• Should be okay, but we should keep on eye on our runner and token usage
• In theory we can set up a budget, but let's not do that yet

Tracking of AI usage

• https://usegitai.com/
• Are we okay to get pr-s with metadata related to AI usage
  • What would be the value for the project here?
    • In theory reviewers could understand better what was generated by AI
    • Price of this is more metadata stored in our git repos
  • It is not something what we would require at the moment
• Are our contributors okay to provide this kind of PRs?

GSoC project (Jaisheesh)

• There is a weekly meeting to follow up the GSoC project. If you want to join ping @CsatariGergely
• GitHub project to follow up the progress: https://github.com/orgs/kptdev/projects/5
• We proposed a tutorial about the OpenTelemetry demo to the Open Source Summit EU 2026
  • CFP Notifications: Friday, 24 July
• 2026-07-15: showed working demo last week ; changing shop front, change of language etc. Progressing well towards completion
• 2026-07-22:
  • @ciaranjohnston is testing the demo, it works well
• 2026-07-29
  • Report is here: Google Summer of Code 2026 Final Report #4661
  • We are finalizing the activities here
  • We are on the schedule of Open Source Summit (https://sched.co/2RabQ)

Porch documentation

• Jump directly to the documentation page of Porch from the kpt and the function-catalog documentation (@Catalin-Stratulat-Ericsson )
  • PRs were done by Catalin
• Phase 2 is a full integration of the Porch documentation to the renewed kpt documentation
• 2026-07-15: no updates
• 2026-07-22:
  • PR-s are merged
  • We should wait with the merger of the two documentation with the kpt documentation reorg

Sonarcloud / FOSSA

• Need a new sonarcloud project: Move relevant repo to new Sonarcloud project #4528
• https://cncfservicedesk.atlassian.net/servicedesk/customer/portal/1/CNCFSD-3528
• 2026-06-03 - 2026-06-10: Waiting for support
• 2026-06-17: We can use SonarCube free tier and Snyk. Porch was added to both. Should we add the rest of the repos?
  • A: Gergely to check if we run FOSSA on Porch
  • We should not block anything based on Snyk things
  • Let's keep running all the things now on Porch and see if we like them
• 2026-07-01
  • A: Gergely to check if we run FOSSA on Porch
  • All automation seems to working right in Porch
  • A: Gergely to propagate the same config to the rest of the repos. Define a composite action and refer to that in other repos.
• 2026-07-08
  • FOSSA badge on Porch Adding FOSSA badge porch#1090 -> merged
  • Config propagation was not done yet
• 2026-07-15
  • @efiacor will look at adding sonarcloud to kpt repo to close this off
• 2026-07-22
  • We need to add the SonarCloud GitHub app and the magic what @efiacor did
  • With the free tier we can not control the gates, but nothing is blocking at the moment
  • Gergely will to the GitHub app install and notify @efiacor
• 2026-07-29
  • Adding SonarCloud config #4657
    • Should be fixed using a local Sonar instance

Roadmap

• Let's use the Jun 24th Community Call timeslot
• Roadmap issues are marked in the kpt and Porch repos
• Gergely made an attempt to configure one GitHub Project which has all issues in the org labelled with Roadmap
• This needs a bit more research
• 2026-07-15 - 2026-07-29: no updates

kpt to v1.0.0

• 2026-05-20 - 2026-07-13: tracking under EPIC: Release kpt version 1.0.0 #4491, we can check weekly on status
• 2026-07-15: slow but steady progress. Not a lot left - tracked under the above issue
  • Need to approve versioning information in governance repo: https://github.com/kptdev/governance/pull/12/changes - this is for @ciaranjohnston and @CsatariGergely
  • also need to approve https://github.com/kptdev/.github/pull/11/changes
• 2026-07-22: @CsatariGergely will check the two pr's later today
• 2026-07-29:
  • @CsatariGergely to re-review the prs
  • @CsatariGergely will ping @ciaranjohnston for Adding Porch Maintainers to the maintainer register governance#11 and Add links to Porch and related kpt plugins .github#11

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-07-29: 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 - 2026-07-29: no update

Clean up the kpt repo

• EPIC: Clean up the kpt repo #4552
• 2026-07-15: 2026-07-29: needs some effort to conclude, some low-hanging fruit that can be easily dealt with

kpt docs versioning

• Use the same approach as with Porch
• We need a kpt 1.0.0 first
• This should be part of the v1.0.0. epic
• 2026-04-08 - 2025-07-29: No progress

Docs reorg

• Remove the book structure - @CsatariGergely
• 2026-04-08 - 2026-07-29: No progress

.project repo rollout

• Keep Maintainer Data Up to Date - @CsatariGergely
• Link GitHub Handles to LFID (@CsatariGergely to post a slack about how to do this)
• Verify Email Settings
• Review and Merge Your PR
• We don't need to immediately do anything - the CNCF will trigger this: https://contribute.cncf.io/blog/2026/04/22/introducing-dot-project-for-maintainers/
• 2026-07-22:
  • We have a .project repo !!!!
  • Onboarding: complete kpt .project setup .project#1
• 2026-07-29:
  • Init .project .project#2 <- check and review!

ADOPTERS.md

• We should look into the adopters file of Metal3

Disable Copilot for additional commits

• AGENTS.md pr needs reviews in kpt
• Gergely will add AGENTS.md-s to the rest of the repos after this one is merged
• 2026-07-01
  • Implemented on Porch by @efiacor and will be moved to the rest of the repos
  • After the kpt AGENTS.md is merged @CsatariGergely will work on a Porch one
  • Utilize copilot.yaml also in the AGENTS.md
• 2026-07-08
  • No progress
• 2026-07-15: no progress, wait until @CsatariGergely returns
• 2026-07-22:
  • No progress
• 2026-07-29
  • Adding AGENTS.md #4573
  • PR was updated, but comments were not addressed

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
• 2026-05-27: Next one is Create library for common utils in kpt functions catalog #2043 on Page 13
• 2026-06-03: Next one is Feature request: Function that sets setter values #2099 on Page 13
• 2026-07-08: Next one is Move kpt live command logs to stderr #2191 on Page 13
• 2026-07-15: added the "needs-analysis" label for items that cannot be considered triaged yet but need to be looked at further
• 2026-07-15: Next one is kpt should notify the user if any resources are not removed from local due to local changes #2241 on page 13
• 2026-07-22: Got to kpt live status provides a misleading error message #2260, next is Create Bot Account for Performing Automated Changes #2264 on page 12