Recipe

dify-ssrf-proxy

The Dify egress proxy on Kubernetes via the helm provider's Workload synthesis (a stateless Deployment plus a ClusterIP Service on the proxy port). The proxy caches in memory only and keeps nothing across a restart, so it renders stateless. The whole Squid configuration is emitted as a ConfigMap via artifacts: and mounted whole-directory, and the container is started against that file directly. Every value the configuration needs is resolved when the stack is compiled, so the rendered file is the final configuration rather than a template a container entrypoint has to expand at startup — which is what lets a reviewer read the effective access rules out of the manifest. The access rules are ordered so that the refusal comes before the permissions: any destination in private, loopback, link-local, shared-CGN or multicast address space is refused, and only then are the named domains and the calling workloads permitted. That ordering is the security property — a supplied address reaches the public internet and cannot reach the cluster's own services or the node's metadata endpoint — so a private range becomes reachable only by being named in allowed_private_networks, which renders ahead of the refusal. provides.host is the bare, self-contained in-cluster service name of the synthesized Service — it carries no namespace, so the recipe is independent of where it is deployed. A consumer in another namespace qualifies the host with the target namespace on its own side (caller-side routing).

Provenance

OfficialSigned by a signing identity this catalog recognizes as an official publisher.
Content digest
sha256:720e43530779d6a0f75996adc878c501e9892fa945b7c5ed386582ee5e4530df
Published
2026-11-10T10:23: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:247a1012c683a7940613131fc636eda3f6803f783714de0892d8eb7219fcc43c

Reference at this version

oci://hub.aggrega.ai/recipe/helm/dify-ssrf-proxy:1.0.0
Target
—
Implements
core/ai-agent/dify-ssrf-proxy:1.0.0

Provides

Deterministic pointer templates this recipe wires for consumers.

NameTemplate
host{{ .context.rendered_name }}-default
port{{ .infra.port }}
protocolhttp

Workload

Workload · form: stateless · replicas: 1 · containers: main

Locals

No locals declared.

Values mapping

No values mapping 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

  • implementsimplementscontract compatible

    core/ai-agent/dify-ssrf-proxy:1.0.0

    All required outputs are satisfied and every provided output is named in the contract.

Used by

Nothing in the catalog depends on this entity.

Recipe 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