Feature

core/egress-allowlist

Lets the component it is attached to connect only to the components it is wired to: the targets of its uses edges, each on the ports its pods declare, plus its own pods, the cluster's DNS and the address ranges the attachment names. It keeps, say, an agent platform reaching only the models and tools its Aggregate wires it to. It restricts where a connection may go, not what it carries. The cluster's network enforces the rule, and only where its network plugin implements network policy, so the Release affirms it. A target the cluster does not run, such as a hosted model API, is reached only through the address ranges the attachment lists for it, and a range admits those addresses on any port for the whole component, not for that connection alone. Attached by the operator in the Release, on the component it restricts, under components.<id>.features. Its destinations are the uses edges the Aggregate already declares, so a connection the Aggregate does not declare as an edge can be refused by the cluster wherever a Release attaches it. Realized on helm: one network policy per workload the component renders, in that workload's namespace. The build halts, naming the connection, where a target renders no pods and no range is listed for it, or where a target declares no port; and, as core/caller-allowlist does, where a workload is emitted into no namespace or carries neither a controller selector nor the build's identity labels. On compose the build halts, naming this Feature: compose has no network policy.

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:7e5d00c49318b456254313ff3121afe9b38ef171291469ba51df485b86014f3a
Published
2026-11-10T10:17:06Z
Signing identity
https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

Signature

  • Officialapplication/vnd.dev.sigstore.bundle.v0.3+json

    https://token.actions.githubusercontent.com/https://github.com/aggrega-ai/aggrega-hub/.github/workflows/catalog-publish-sign.yml@refs/heads/main

    sha256:69a823bfbd7fabd9cbef312150fe49bc43aafd8fc074d6c04257733ad393e0db

Reference at this version

oci://hub.aggrega.ai/feature/core/egress-allowlist:1.0.0
Applies to
component.aggrega.ai/type in (server, stateful-server, worker, task, function)
Conflicts with
—

Developer parameters

Values the developer sets when attaching this feature.

No developer parameters declared.

Output contract

Values this feature publishes to consumers.

No output values declared.

Annotations

No annotations declared.

Relationships

Typed edges to and from other published entities. A reference with no published target renders as a broken edge rather than a link.

Uses

Used by

Feature concept reference →

The Aggrega catalog — an open index of components, features, recipes, and the plugins that render them.

Built with the shared Aggrega design system.

Privacy