From 9bea3135cf0e2930b712a1973c0af1f66dfd0971 Mon Sep 17 00:00:00 2001 From: aevesdocker Date: Mon, 2 Feb 2026 14:47:50 +0000 Subject: [PATCH 1/2] Compose: Bridge for orgs --- content/manuals/compose/bridge/_index.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/manuals/compose/bridge/_index.md b/content/manuals/compose/bridge/_index.md index 2c795fd27aa5..fcdc25e97bdc 100644 --- a/content/manuals/compose/bridge/_index.md +++ b/content/manuals/compose/bridge/_index.md @@ -33,6 +33,12 @@ Compose Bridge also supports applications that use LLMs via Docker Model Runner. For more details, see [Use Model Runner](use-model-runner.md). +## Apply organizational standards at scale + +Docker Compose Bridge can help companies to apply organizational policies through custom transformation templates that are applied when converting `compose.yaml` files to Kubernetes manifests. Developers continue to write standard Compose files, while required security contexts, resource limits, labels, and network policies are applied automatically and consistently during conversion. + +When requirements change, platform teams update the templates once and all teams inherit the changes on their next deployment. This separation lets developers focus on application configuration while platform teams or organization administrators manage governance. + ## What's next? - [Use Compose Bridge](usage.md) From 162d2d0b0f75f261a807cae370bcf6f6837ae1d9 Mon Sep 17 00:00:00 2001 From: aevesdocker Date: Fri, 27 Feb 2026 13:50:54 +0000 Subject: [PATCH 2/2] edit --- content/manuals/compose/bridge/_index.md | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/content/manuals/compose/bridge/_index.md b/content/manuals/compose/bridge/_index.md index fcdc25e97bdc..81a91acab614 100644 --- a/content/manuals/compose/bridge/_index.md +++ b/content/manuals/compose/bridge/_index.md @@ -35,9 +35,24 @@ For more details, see [Use Model Runner](use-model-runner.md). ## Apply organizational standards at scale -Docker Compose Bridge can help companies to apply organizational policies through custom transformation templates that are applied when converting `compose.yaml` files to Kubernetes manifests. Developers continue to write standard Compose files, while required security contexts, resource limits, labels, and network policies are applied automatically and consistently during conversion. +## Apply organizational standards at scale -When requirements change, platform teams update the templates once and all teams inherit the changes on their next deployment. This separation lets developers focus on application configuration while platform teams or organization administrators manage governance. +Compose Bridge supports custom transformation templates, which lets platform teams encode +organizational standards once and apply them consistently whenever a `compose.yaml` file +is converted to Kubernetes manifests. + +Developers continue to write standard Compose files. During conversion, Compose Bridge +runs your custom transformation and automatically injects the required security contexts, +resource limits, labels, and network policies into the output manifests — without +requiring developers to know or manage those details. + +When your requirements change, update the transformation template in one place. Every team +picks up the changes on their next conversion, with no edits to individual Compose files. + +This separation of concerns keeps developers focused on application configuration, while +platform teams control governance and enforce policy through the transformation layer. + +To get started, see [Customize Compose Bridge](/manuals/compose/bridge/customize.md). ## What's next?