2026-03-11 SIG-2 Agenda & Minutes

2026-03-11 SIG-2 Agenda & Minutes

Community Attendees:

@Liam Fallon

@Rendre Greyling

Anubhav Das

@Aravindhan Ayyanathan

@Catalin Stratulat
@Kushal Harish Naidu

Community Attendees:

@Fiachra Corcoran

@James McDermott

@László Mózes

@Gergely Nagy

@Viresh Navalli

LF Staff:

Agenda

Antitrust Policy

Minutes

Create Remote Fetches

Enable go-git caching

API v1alpha2 PR

  • Ready for review, please review.

Proposed Branching Strategy

  • Switch branching strategy to have a maintenance 1.5 branch for the existing Porch

  • Merge feature-1.6 to main and continue the main development on main, bringing in new changes there. So main would be released as 1.6.x for Nephio R7

  • If necessary we do CVE updates/bug fixes or urgent small changes on the 1.5 branch and do 1.5.x releases off this branch, this branch will not get any major new functionality

  • We will provide an upgrade path from 1.5.x to 1.6.x

Should we remove CR Cache?

  • CR Cache makes the implementation more complex

    • PackageRev/PackageRevision tracking for consistency

    • Webhook for PackageRevision deletion has a 30 second timeout (even though we have a 290 second timeout in the API server)

  • Should the CR cache be deprecated first and then removed? That would be the proper approach.

  • In the PackageRevision CRD work we don’t need the PackageRev CRD any more

    • PackageRev CRD won’t be needed once we have the PackageRevision CRD

    • Will we need a CR cache at all then?

  • Let’s work out the design of the PackageRevision CRD epic first and then see where we stand with the CR cache.

  • Using the PackageRevision CRD directly towards a git backend is in effect the same as the CR cache we have today

Webhooks for Deletion

  • Are Webhooks inherently slow, will this cause problems for the CRD PackageRevision work?

    • Why is the package deletion slow? It might need to list all the PRs?

    • Maybe don’t use validation int he weebhook and don’t do it

testcurrentdeletes e2e test

  • This test is flaky, @Rendre Greyling may have a solution, @Aravindhan Ayyanathan and @Rendre Greyling will chat on this

  • For flaky tests, “gotests” has a flag to rerun the tests if they fail. We should see if we can turn this flag, it will rerun all tests that failed. @Liam Fallon @László Mózes and @Fiachra Corcoran will check this

Push DB Cache drafts to git

  • Ready for review

  • Memory performance of go git is not great

More meaningful error messages

Action items