Agenda

Action Items Review
Update on Porch proposed move to kpt
- Decision will be made by Nephio TSC on 2026-04-23
Can “Proposed” be optional?
PackageRevisionResources update
DosuBot documentation PRs
PR Triage
Slack retirement
Issue Triage
AOB

Minutes

CRCache removal

Issue created? @Nagy Gergely
Update from @Fiachra Corcoran
- The CRD implementation will have a completely new cache type
- Proposal is for Current CR Cache and DB Cache to be deprecatd

Can the “Proposed” state of a PR be optional?

People often do a Propose/Approve one after another
For large packages and many approvals in parallel, it has a performance hit
“Proposed” step will still exist but will be possible to skip
Users with a special role would be able to set the state of a PR from Draft to Approve
Of course, the mutation and validation pipelines must be passing on the draft
It looks like the PR will be straightforward
Neither Propose nor Approve should start a render, they simply should fail immediately if the mutation/validation pipelines are not “clean”
Concerns?
- Will the implementation make “engine” and other parts of Porch more complex?
- Large documentation changes?
- How will Approval work in the new CRD work?
A PR will be raised for this

PackageRevisionResources update

We are not just taking the yaml files and storing them but there is a “healing” process that is carried out
We should assume that the client knows what it is doing and just update the resources with the incoming yaml
The current approach also consumes resources during the update
If we remove the healing, will it have an impact on existing usages of Porch by stakeholders.
A PR will be raised for this

CRD Related work

Dosubot PRs

Not working correctly on the Porch repo
Let’s wait until the proposed kpt move before fixing this as Dosubot works better in kpt

Slack Retirement