Community Meeting 2025-10-15

[CsatariGergely]

Attendance

• @liamfallon
• @timop62
• @CsatariGergely
• @efiacor

Topics and action items

CODEOWNERS

• Gergely will add Timo to the governance repos and @kispaljr will provide a name for the rest of the repos

Actions from the Nephio dev event (#4254)

Enhancements

• Reasons for kpt file and ConfigMap separation
  • We should have an issue with low priority -> @liamfallon (Allow configuration to be placed in the Kptfile #4268)
• Mutation/Validation pipelines during upgrades
  • We should have an issue -> @liamfallon (Allow Mutation and Validation pipelines to run during upgrade #4269)
• Prevent formatting the kptfile during upgrades
  • Keep the original comments and formatting of kptfile
  • In the new SDK there is a go package called kptfile. Using this go package will preserve most of the formatting.
  • We need an issue to change the kpt to use the kptfile go package -> @lapentad
• Inline curated kpt functions (maintain a set of curated kpt functions which can be run without pulling stuff from docker hub)
  • Needs an issue -> @liamfallon
  • Let's start to list the functions what we use (starlack, apply-replacement)
  • An option is to use the built in runtime from Porch
  • Gradually we should inline all the KRM functions
• Remove not used KRM functions (fix, kubeval and maybe the GCP functions) -> @efiacor
  • Figure out which ones are used first.
    • e.g.: kubeval is used, but needs a rewrite (#4258)
• Separate validation pipelines
  • Git + OWNERS file can enforce rules
• Create new KRM functions (kubeconform to replace kubeval)
  • (#4258)
  • Convert kubeval to kubeconform in golang krm-functions-catalog#1181 was created, needs reviews
• Have a convenient way to build the docker files -> @CsatariGergely
  • Have a command what will produce a ready KRM function including the Docker file. Clarify with Gergely Nagy.
• 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
• Allow to break the pipeline from the kpfile resource -> @kispaljr
  • Define the pipeline in a separate file
  • This allow us to separate the pipelines like mutation pipeline and validation pipeline
  • Open up the possibility to have different kind of pipelines
  • In the far future we can make the pipelines pluggable, like create other pipelines not implemented in kpt, like Ansible, GitLab or whatever
• Issue handling
  • Kill issues obviously non replaceable or Porch related
  • Prioritize new issues
  • A: Gergely to organize a meeting to review the issues.
  • Set up Slack "fire hose" for the maintainers
    • It is a bit difficult as the kpt channel is in the Kubernetes Slack
    • We will no go for this for now
• Move Porch to use kpt.dev version of kpt instead of GoogleContainerTools version of kpt
  • This needs EPIC: Transfer of kptdev repositories from GoogleContainerTools #4259 to be fixed
  • Needs an issue on Porch -> @liamfallon (Switch Porch to use the kptdev version of kpt nephio-project/nephio#976)
• All changes done in the krm-function-sdk in the Porch fork will be moved to the upstream kpt.dev version of the repo and Porch will use the functions from kpt.dev (#4229)
  • @kispaljr is working on using the kpt.dev sdk instead of the Nephio fork
• ensure if a pipeline run in kpt and in Porch the same thing will happen
  • Create an epic about these -> @liamfallon (EPIC: Align the kpt pipeline execution in kpt and Porch #4271)
  • The best way to achieve this is to run the same codebase
  • The pipelines can run by executors. The different executors can have different results. This is not good.
  • Executors are all over the place. We should have a better structure for the executors.
  • A kpt package would not always work in Porch and vice versa. This should be fixed.
  • We need to study mutation pipelines
    • Can we move the Porch mutation pipelines to kpt?
  • 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
• In the Porch repo there is a kpt folder #4229
  * These should be included from kpt.dev
• We should stop using the wet/dry analogy from the docs. It is confusing for users -> @CsatariGergely
• Clean up the kpt repo
  • Lets keep it here and target later

KubeCon NA 2025

• We have the timeslot on Tuesday 3:30 PM - 7:45 PM
• Volunteers: @CsatariGergely , @liamfallon
• Demo
  • ngnx demo
  • change the kubeval krm function to kubeconform one
  • We should try it after the references are fixed
• Slides
• Logo

Container registry set up in github - @efiacor - tracked with #4195

• Migrate fn image publish and release to ghcr.io
• Related discussion in Migrate fn images to ghcr #4210
• Issue to move KRM Functions Move go krm fn images to ghcr publish mech #4220
• Primary target: Release process will publish only to ghcr.io in the future
• Stretch target: We should make the old images from gcr available in ghcr.io
• Agreed 2025-07-09: Deprecate the typescript images - @efiacor @kispaljr are already deprecating the SDK capabilities
  • keep the starlark functions
  • Add a deprecation notice to the documentation and a message to the slack

krm-function-catalog documentation move to Hugo

• Redirect https://catalog.kpt.dev/ to Netlify
  • https://jira.linuxfoundation.org/plugins/servlet/desk/portal/2/IT-28808

take a discussion with @michaelvl on krm functions catalog - @liamfallon @kispaljr

• 2025-09-03: Still no feedback from MichaelVL. Maybe we will have a chance to discuss on KubeCon

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

kpt docs

• Dominika is working on the Porch documentation. We should move all the commands which were moved to Porch
• We should doublecheck if the alpha command is still in the kpt command line

Logo

• Design proposal is here
• Logo needs to be uploaded to https://github.com/cncf/artwork 8 weeks before KubeCon
• We are all very happy with this. This will be the new logo of kpt

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

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

• Transfer of the trademarks / contribution agreement

Some repos still have master

• Let's do it right after KubeCon

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

• Did some triaging and got down to What RBAC permissions for live apply? Correct values for apiGroups and resources #4095
• To be continued

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

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

• A: Gergely to start a discussion on Slack about this

There will be a Cloud Native Telco Day EU 2026

• CFP is open
  • Resurrecting kpt story
• KubeCon EU 2026 CFP is also open