Technical Meeting 2026-06-17

[liamfallon]

Agenda

1. Action Items Review
2. Priority PRs

• Documentation for Porch subpackage clone and upgrade support and minor fixes porch#1038 @liamfallon
• Any others?

3. Issues raised by @kispaljr
4. Downgrading k8s.io/ modules to v0.34.x and controller runtime to v0.22.x @mozesl-nokia
5. Test build of main, pre-release of 1.6.0
6. Github action for releasing Catalog functions: GitHub action for bumping up the patch versions of catalog functions #4588
7. Status of "Parallel mutation pipelines" PIP: Async pipeline executions porch#871
8. PR Triage
9. AOB

Attendance

• @zaadnsu

• @aravindtga

• @efiacor

• @CsatariGergely

• @nagygergo

• @JamesMcDermott

• @kushnaidu

• @mozesl-nokia

• Oisín Johnston

• @rendre-greyling

• @timop62

• @liamfallon

• • @kispaljr

• If you are not in the attendance list add your GitHub handle to a comment under the discussion

Minutes

@liamfallon chaired the meeting.

Deprecation timeline for the Porch v1alpha1 API

Thought is to set deprecation on v1alpha1 at the beginning of Q3 2026 and remove v1alpha1 at the beginning of Q2 2027, check with stakeholders @kispaljr

• 2026-05-13: Waiting on response @liamfallon @mozesl-nokia
• 2026-05-20: Waiting on response @liamfallon @mozesl-nokia
• 2026-06-03: The timeline is ok for @mozesl-nokia
• 2026-06-10: @liamfallon to provide input on this.
• 2026-06-10: @liamfallon keep v1alpha1 API support until the end of Q2 2027.
• 2026-06-10: @rendre-greyling we may need to keep v1alpha1 API support until the end of Q3 2027.

Flaky e2e tests

• Some PRs have been merged on this
• PR up to fix the deployment issue Improve CI deploy reliability, move CR cache tests to nightly porch#1002
• Please jump in and try to fix issue if you see them
• Improve CI deploy reliability, move CR cache tests to nightly porch#1002 is merged now and it seems that it solves most of the issues. Yey!
• 2026-06-10:
• kpt live destroy deleted the porch server before the function config finished so the function config was hanging there
• kpt live apply being stuck has an outstanding issue live apply stuck #3395
• 2026-06-17
• kpt live apply still having issues, should we move to use kubectl apply and a watch
• kpt live apply can delete resources, all of your apply has an instance ID on resources that allows resources to be deleted
• kpt live destroy hauses problems in the sequence of shutdowns

## Github performance

• Should we consider an alternative to Github?
• There are no hard rules to use Github but it is the best supported platform
• Let's kick this to the community meeting next week as a topic.
• 2025-05-27: The CI test reliability seems to have improved due to the actions we have taken.
• 2026-06-03: @CsatariGergely to check with CNCF if it is mandatory to use GitHub as a development platform
• 2026-06-10: No Progress
• 2026-06-17: No answer yet from CNCF

Inactive PRs

PRs that have gone "stale", that there has been no action on for a period of 4 weeks should be closed with a comment stating that the PR can be reopened at any time by the author if they feel they want to.

• 2026-06-03: Let's just set the rules first. @CsatariGergely add to CONTRIBUTING.md
• 2026-06-10: No progress
• 2026-06-17: No progress

Condition type discussion

• We will continue to use the custom condition type in kpt rather than the k8s one
• We should check duplicate types across Porch and kpt and see if there is some cleanup required. @liamfallon to come back next week on this.
• 2026-06-10: No Progress

## Downgrading kpt to run on older versions of k8s and controller runtime

• The latest kpt causes problems due to a dependency that expects an older version of the controller runtime
• Keep 0.36 as long as we can and in the future only upgrade to newer k8s versions when we absolutely have to
• Because kpt code is used as library functions, code that imports kpt may not work.
• We should not be on the leading edge but we should not fall too far behind either, maybe n-1
• Only do patch updates as long as we can and then plan for the jump to the next minor version of k8s and controller runtime, planned in conjunction with minor version upgrades in kpt
• Decision: Plan upgrades in a more controlled way from now on

Test release of 1.6.0

• Let's go ahead and test it (1.6.0-test)

Github action for releasing Catalog functions

• This will be very useful
• We need to test it, we should merge feat(set-labels): migrate to SDK v1.0.4 with WithDocs support krm-functions-catalog#1258 and merge the catalog PR
• Try the catalog github action with the new set-labels function

Parallel mutation pipelines

• On hold for now.
• The parallel function runner is implemented
• We need some days together to come up with an architecture for the next 2-3 years

Note

We reached this point in the agenda at the meeting

PRs to be reviewed

Porch

• WIP: Create remove fetches porch#246: This PR is to be moved into an issue because the PR is too old to easily merge, but the function it implements would be good to have @nagygergo
  • 2026-06-03: @liamfallon or @nagygergo to create an issue about this
  • 2026-06-10: No progress
• porchctl improvements porch#554: On hold, PR 541 must be merged first
  • 20256-05-27:Reduce code duplication across rpkg CLI commands porch#541 is merged so we can proceed with this one now
  • 2026-06-03: porchctl improvements porch#554 needs to be reworked
  • 2026-06-10: No Progress
• WIP: Refactor Performance Tests and add Grafana, Pyroscope and Prometheus monitoring stack porch#561:
  • 2026-06-03: Comments are addressed. Waiting for Add OpenTelemetry metrics for package resources size porch#1018 andneeds to implement more metrics. On hold at the moment.
  • 2026-06-10: Waiting on Support more flexible logics #1018
• PackageRevision controller architecture docs (draft) porch#971: In Draft, not addressed comments
• Add documentation for FunctionConfig CRD and reconciler porch#976: In Draft, still on hold
• docs: add versioned docs build with tag-based snapshots porch#980: CoPilot comments, no progress
• Upgrade Go/kpt dependencies and disable govet inline analyzer porch#1017: Under review
• Go linter: Using the latest version can result in breaking the CI. It's better to use concrete versions.
• Add OpenTelemetry metrics for package resources size porch#1018: Ready for review
• FunctionConfig controller improvements 1 porch#1019: In draft
• Add porchctl implementation for clone and upgrade of independent subpackages porch#1022: Ready for review, some copilot comments.
• Debulleting the Porch Troubleshooting pages porch#1024: Ready for review
• Docs main placeholder pr concept porch#1026: Ready for review by @nagygergo
• Cherrypick subpackage clone and upgrade support to 1.5 branch porch#1027: Ready for review
• resolve fieldmanager type conversion warning and WatchList bookmark panic porch#1035: Ready for review
• Documentation for Porch subpackage clone and upgrade support and minor fixes porch#1038: Work in progress
• Return log messages in a single line for successful render with stderr porch#1039: CoPilot comments

krm-functions-catalog

• feat: port generate-folders function from TS to Go krm-functions-catalog#1216
• 2026-06-10: Dormant
• Add foo, bar, printenv and drop-comments test helper functions krm-functions-catalog#1256
• 2026-06-10: Ready for review
• feat(set-labels): migrate to SDK v1.0.4 with WithDocs support krm-functions-catalog#1258
• 2026-06-10: Ready for review

krm-functions-sdk

• 2026-06-10: All clear

kpt-backstage-plugins

• 2026-06-10: Dependabot PRs

kpt

• Replace random generated "inventory ID" #4396 - Needs rebase, but ready for review
• 2026-05-27: Work in progress
• 2026-06-03: Closed and feat: Add CEL-based conditional function execution (#4388) #4469 opened as a clean rebase
• Docs/wasm function support #4419 - Community must decide if we wish to document the WASM functionality and decide whether to merge this PR or not, add to agenda for the community meeting next week.
• 2026-05-27: WASM support is experimental, we should just mention that in the documentation and not mention WASM support further. @Catalin-Stratulat-Ericsson will raise a PR to add a statement on WASM support that it's experimental.
• 2026-06-03: Let's try to get Docs/wasm function support #4419 merged. Needs to address Copilot comments and Netlify build error.
• fix(update): preserve Kptfile formatting during upgrades #4427
  • 2026-03-18: needs rebasing and some copilot comments to be resolved. This could be very problematic to resolve ... needs a careful review
• 2026-04-22: Comments still not addressed
• 2026-05-06: Coments are addressed, @Jaisheesh-2006 will present this PR at the kpt technical meeting next week.
• 2026-05-27: We'll wait for @mozesl-nokia to review
• 2026-06-03: Waiting for one more persons review and a rebase.
• Split/fn eval namespace #4444 - has unadressed comments
  • On hold for now
  • 2026-05-27: This work can be picked up again now.
  • 2026-06-03: Needs to address Copilot comments and rebase. @liamfallon why do we have the do-not-merge/hold label on this?
• feat: Add CEL-based conditional function execution (#4388) #4469 - address Copilot comments, Tests are failing, new PR with rebase of feat: Add CEL-based conditional function execution (#4388) #4391
  • 2026-05-06: The work for the v1 API will clean up the tests tat are causing this PR to fail, we should put this on hold and merge it once the tests are fixed.
  • 2026-05-27: Waiting on the test update
  • 2026-06-03: Should try the tests now, should rebase, should fix DCO
• Proofreading chapter 2 #4487 - Needs to address Copilot comments
  • 2026-05-06: Outstanding comments
  • 2026-05-27: Ready for review
  • 2026-06-03: Needs one more approval
• Proofreading chapter 3 #4534
• 2026-05-27: Copilot comments to be addressed
• 2026-06-03: Copilot comments to be addressed
• Make API it's own go module #4537
• 2026-05-27: Under review
• 2026-06-03: Needs reviews
• Custom logic for 3-way-merging null values #4542
• 2026-05-27: Ready for review
• 2026-06-03: Needs reviews. @mozesl-nokia to add tests