2025-02-19 SIG-2 Agenda & Minutes
Community Attendees:
@Liam Fallon
@Daniel Kostecki (Red Hat)
@Fiachra Corcoran
@balaji varadaraju
@Girish Kumar
Community Attendees:
@Istvan Kispal
@James McDermott
@Prashant Mishra
@Vishwanath Jayaraman
LF Staff:
Agenda
Antitrust Policy
Action Items Review
Status check on items for Nephio R4
O2 IMS
FOCOM
SPIFFE: Workload Identity
Flux Controller
Platform improvements/Code Freeze
UI Improvements
Overall opinion on the status
Execution of and Status of the release activities
Next week’s meeting
Minutes
kptdev
On kptdev, @Vishwanath Jayaraman reported that there was no response on the channel and tle last monthly kptdev meeting was in October
Issues outstanding
Carried forward to the next meeting
SPIFFE
If the Nephio controller gets deployed first and the SPIFFE operator gets deployed after, then the Nephio operator can’t pick up on the SPIFFE operator
If you deploy this file catalog/nephio/optional/spire-agent/spiffe-csi.yaml at main · nephio-project/catalog and then deploy the Nephio operator then it will work
We need to put SPIFFE as an optional package for this reason
Also organizations may choose to use another approach other than SPIFFE for workload identity management so it makes sense for the controller to be optional
The change to the Nephio controller needs to be reverted and a custom SPIFFE nephio controller needs to be added to the optional packages (Change in the Catalog repo), a PR will be raised for this later this evening
Other R4 Items
Code/Catalog/API/test-infra for everything else is done
Docs on O2-IMS add usecase user guides for the o2ims operator by vjayaramrh · Pull Request #209 · nephio-project/docs
Docs on FOCOM
Flux docs are done
UI is done
Overall Status
Just the docs and the SPIFFE catalog
Release check list slide set for TSC: https://docs.google.com/presentation/d/1pg5ku8JrxXvdb53G8RpkePWZmfvFYduwD_o2x5ReYVg/edit#slide=id.g2b0ea95d9db_2_8
Release Activities
Nephio and porch repos are being tagged
We’ll move the checklist onto the wiki
R5
We’ll go through the R5 story list at the next meeting, R5 Planning
We can create a project for R5 in Github
Technical debt needs to be addressed, code coverage, code smells (Sonarcloud etc)
Mentoring of new volunteers
Next Week’s meeting
Many people are not available
Next weeks meeting will be cancelled
Next meeting will be on the 5th of March