Planned - Nephio: Porch PackageRevision as a CRD

Short Description

Topic Overview

Today, Porch directly manages PackageRevision resources using the Kubernetes API server. This means that porch mus implement (or re-implement) much resource handling that is supported in Kubernetes for CRDs. The main reason for Porch not implementing a PackageRevision as a CRD is because the package contents of a PackageRevision (its PackageRevisionResources) can be very large, too large to post as a CR. This issue describes the problem well: https://github.com/nephio-project/nephio/issues/598

Using the kubernetes API server has issues which are causing significant problems in Porch such as the hard-coded timeout on API operations of 34 seconds. This has resulted in Porch cloning the kubernetes API server code into Porch in this PR: https://github.com/nephio-project/porch/pull/300

This session will examine Porch and see what effort is required and what steps are needed to change Porch to use a CRD.

This session is related to Planned - Nephio: Asynchronous operations in porchPreview , in that moving the PacakgeRevision resource to a CRD will mitigate problems with asynchronous operations.

Session Type

Slides & Recording

Notes From Session (as appropriate)

Action Items (as appropriate)