Design Decisions

Mon, 01 Jan 0001 00:00:00 +0000

Overview

This page explains the key architectural decisions that shaped the Repository Controller, focusing on the “why” rather than the “what.” Each decision represents a deliberate trade-off made to balance competing concerns like performance, reliability, and operational simplicity.

These decisions address fundamental challenges in distributed systems: how to detect failures quickly without wasting resources, how to handle errors intelligently, and how to provide clear operational visibility. Understanding the rationale helps when troubleshooting issues or considering configuration changes.

Component Interactions

Mon, 01 Jan 0001 00:00:00 +0000

Overview

The Repository Controller operates within the Porch ecosystem by watching Repository custom resources and interacting with the cache layer to keep package metadata synchronized. This page describes how the controller integrates with other Porch components.

Architecture

┌────────────────────────────────────────────────────────┐
│ Repository Controller │
│ │
│ ┌─────────────────────────────────────────┐ │
│ │ Reconcile Loop │ │
│ │ │ │
│ │ • Watch Repository CRs │ │
│ │ • Sync Decision Logic │ │
│ │ • Async Workers │ │
│ │ • Status Updates │ │
│ └─────────────────────────────────────────┘ │
│ │ │
│ ↓ │
│ ┌──────────────────┐ │
│ │ Cache Interface │ │
│ │ │ │
│ │ • OpenRepository│ │
│ │ • Refresh │ │
│ │ • List Packages │ │
│ └──────────────────┘ │
└────────────────────────────────────────────────────────┘
 ↓
 Kubernetes API
 ↓
 Repository CRs
 ↓
 Cache Layer
 (CR/DB Cache)

Kubernetes API Interactions

The controller watches Repository custom resources using standard Kubernetes controller patterns. When repositories are created, updated, or deleted, the controller receives events and reconciles the desired state with actual state.

Repository Controller on Porch Documentation

Design Decisions

Overview

Component Interactions

Overview

Architecture

Kubernetes API Interactions