Skip to main content

Architecture

The Marketplace customer bundle is a focused deployment system rather than a large service mesh. The architecture is centered on one primary execution workload and a small number of supporting control surfaces.

Core runtime components

Helm chart

The Helm chart under manifest/chart/ is the primary deployment unit. It defines:

  • the execution Job
  • the Marketplace ubbagent sidecar
  • storage mode selection
  • service account and Workload Identity wiring
  • resource profile selection
  • the Marketplace Application object and related Kubernetes resources used by the supported customer bundle

Kubernetes Job

The main computational workload runs as a Kubernetes Job. This is the unit that:

  • reads inputs from the configured storage root
  • executes the audit pipeline
  • writes outputs under the configured output root
  • calls the entitlement service during the run lifecycle

Marketplace schema and Application CR

schema.yaml collects Marketplace UI inputs and maps them into Helm values. manifest/application.yaml groups the deployed resources into a single application object for Marketplace-oriented management.

Entitlement + Seal API

The runtime calls the external Cloud Run entitlement service for:

  • entitlement availability checks
  • consumption
  • run start recording
  • run completion and seal issuance

Storage layer

The chart supports:

  • PVC-backed storage
  • GCS-backed storage via GCS Fuse on GKE

Supporting runtime components

ubbagent

The Marketplace reporting sidecar is required for the supported Marketplace-metered deployment path.

Console

The current supported customer bundle does not deploy console resources.

Architecture boundaries

The important boundaries in this deployment are:

  • cluster workload versus external entitlement service
  • input staging versus run-scoped outputs
  • customer execution path versus Marketplace billing path
  • reproducibility and seal artifacts versus ordinary runtime logs

This architecture is intentionally narrow. It reduces support surface area for the customer deployment package.