Agenda

Action Items Review
Demo of CRD implementation in Porch @Fiachra Corcoran
FunctionConfig CRD readiness @Laszlo Mozes (Nokia)
- Cache warmup rewrite?
- Docs as follow up?
Golang upgrade.
https://github.com/nephio-project/nephio/issues/1109
https://github.com/nephio-project/nephio/issues/1110
PR List Triage
Issue Triage
AOB

Minutes

PackageRevisionResources Healing

Force Pushing to git

Currently force pushing is off, see https://github.com/nephio-project/porch/blob/main/pkg/externalrepo/git/git.go#L1453
Repositories to which Porch is writing should only be written to by Porch, if they are written directly (outside of Porch), this could result in inconsistent PRs and we can’t say what the result of such changes could be. For example, the “magic” porch tag may not be there or may not be correct in a manually applied commit
Porch can read PRs from “read-only” repos manually managed (or managed by other systems) (read-only Porch repo)
Should we change the git force push flag to “true”? Check with stakeholders.

CRD PackageRevision

Interrupting a render after a push should be possible
Do we allow 2 PRs CRs pointing at the same ns/repo/package/pr
- This might be possible
- We might need mutex protection on git
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

FunctionConfig CRD

High Availability

https://github.com/nephio-project/nephio/issues/1109
A small change on the API server, Use the “manager.Runnable” to wrap the API server
It’s a Active/Standby approach
This will be raised as a PR

Enable Access to a single file