Skip to content
AggregaAggrega
Select language: English

Advanced platform — a multi-boundary Kubernetes platform

A multi-boundary Kubernetes platform that combines several mechanisms in one build from a single Developer-authored Aggregate: boundary-scope FeatureRecipes, parameter hoisting, the credential subsystem, and cross-boundary references resolving through Service DNS.

What it demonstrates

  • Boundary-scope FeatureRecipe — a shared-config ConfigMap rendered once per boundary (executionScope: boundary), not once per component.
  • Parameter hoisting — a typed Aggregate parameter (the Adminer UI theme) the Release fulfils per environment, flowing into a standard developer value.
  • The credential subsystem — a black-box secret slot and a transparent one (core/secret-value, core/secret-provided) delivering passwords into the database via the inject pipe.
  • Cross-boundary String Pipe — the app boundary’s Adminer reaches the data boundary’s database by the host the database Recipe provides, routed across the boundary seam without the compiler interpreting the string.

Consumes the standard library

This example consumes the standard catalog: core/datastore/mariadb, core/devtool/adminer, core/secret-value, core/secret-provided, and core/shared-config (with their helm FeatureRecipes env-secret, provided-secret, and shared-config), the adminer recipe, and the helm provider all ship in the standard library. The mariadb-bitnami Recipe is carried locally by this example — an enterprise-authored sourced Recipe under its own catalog/ directory.

This example’s own teaching scaffolding lives in the shared catalog under the example/ publisher, alongside the standard library:

  • example/db-binding — a Feature (and its FeatureRecipe) that carries the databases use-edge wiring Adminer to the database, specific to this stack’s binding lesson.

It builds against the catalog directory listed under catalog_dirs in .aggrega-config.yaml, the example’s own local catalog/, which carries the mariadb-bitnami sourced Recipe. The Component, features, and remaining recipes resolve from hub.aggrega.ai, the default registry the same file declares, so neither command needs a --catalog flag. The pull fetches the Bitnami chart the sourced Recipe names and pins it, with every entity, in release.lock; the build reads that lockfile:

Terminal window
aggrega pull --release release.yaml
aggrega build --release release.yaml

Scaffold the example

You can build this example with the commands below, or have your AI assistant build it for you.

Write the example into a new folder named after it:

Terminal window
aggrega scaffold --example advanced-platform

It then prints the commands to run next. The first changes into the new folder:

Terminal window
cd advanced-platform

Build

The pull resolves the lockfile, fetching the Bitnami chart the local Recipe names, and the build reads it:

Terminal window
aggrega pull --release release.yaml
aggrega build --release release.yaml

With an AI assistant

An AI assistant set up with Aggrega’s tools can do the same: paste this prompt into it.

Use the Aggrega tools only, and create no folder yourself. If the Workspace folder holds no `advanced-platform` folder yet, call the `scaffold` tool once with `example` set to `advanced-platform` and no `dir`: it writes the example into a new `advanced-platform` folder. Then call the `build` tool with `workspace_root` set to `advanced-platform`, `release` set to `release.yaml`, `auto_pull` set to true and `write` set to true. Tell me which files the build wrote; they are under `advanced-platform/dist/`.