/docs/5_architecture_and_components/controllers/packagerevision-controller/Recent content in PackageRevision Controller on Porch DocumentationHugoen-us/docs/5_architecture_and_components/controllers/packagerevision-controller/design/Mon, 01 Jan 0001 00:00:00 +0000/docs/5_architecture_and_components/controllers/packagerevision-controller/design/<h2 id="controller-structure">Controller Structure<a class="td-heading-self-link" href="#controller-structure" aria-label="Heading self-link"></a></h2> <p>The PR Controller is a standard <a href="https://github.com/kubernetes-sigs/controller-runtime" target="_blank">controller-runtime</a> reconciler. Its internal structure mirrors the reconciliation pipeline, with each concern handled by a dedicated sub-reconciler that returns early if its work is not needed:</p> <pre tabindex="0"><code>PackageRevisionReconciler ├── reconcileFinalizer() — Finalizer + ownerReference management, deletion gating ├── reconcileSource() — One-time package creation (init/clone/copy/upgrade) ├── reconcileRender() — KRM function pipeline execution └── reconcileLifecycle() — Git lifecycle transitions, revision numbering </code></pre><p>For detailed behaviour of each phase, see the <a href="/docs/5_architecture_and_components/controllers/packagerevision-controller/functionality/">Functionality</a> section.</p>/docs/5_architecture_and_components/controllers/packagerevision-controller/interactions/Mon, 01 Jan 0001 00:00:00 +0000/docs/5_architecture_and_components/controllers/packagerevision-controller/interactions/<h2 id="component-interaction-overview">Component Interaction Overview<a class="td-heading-self-link" href="#component-interaction-overview" aria-label="Heading self-link"></a></h2> <pre tabindex="0"><code> ┌─────────────────────────────────────────────────────────┐ │ User / GitOps │ └───────────┬─────────────────────────────┬───────────────┘ │ kubectl apply │ kubectl get PRR ▼ ▼ ┌───────────────────────────────────────────┐ ┌─────────────────────────────┐ │ PackageRevision CRD (etcd) │ │ Porch API Server │ │ │ │ │ │ • spec.source (init/clone/copy/upgrade) │ │ • PackageRevisionResources │ │ • spec.lifecycle (Draft/Published/...) │ │ • Engine (content access) │ │ • annotations (render-request) │ │ │ └───────────────────┬───────────────────────┘ └──────────────┬──────────────┘ │ watch │ read/write ▼ ▼ ┌───────────────────────────────────────────────────────────────────────────────┐ │ Shared Cache (ContentCache) │ │ │ │ GetPackageContent · CreateNewDraft · CreateDraftFromExisting │ │ CloseDraft · UpdateLifecycle · DeletePackage │ │ │ └───────────────────────────────────────────────────────────────────────────────┘ ▲ populated by │ git operations │ ▼ ┌───────────────────────────┐ ┌───────────────────────────┐ │ Repository Controller │ │ Git Repository │ └───────────────────────────┘ └───────────────────────────┘ </code></pre><h2 id="repository-controller">Repository Controller<a class="td-heading-self-link" href="#repository-controller" aria-label="Heading self-link"></a></h2> <p>The PR Controller and Repository Controller never communicate directly. Their coupling is entirely through the shared cache: the Repository Controller creates it, populates it by syncing Git repositories on schedule, and the PR Controller reads from and writes to it.</p>