Skip to content

Compose: Bridge for orgs #24056

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
aevesdocker wants to merge 1 commit into
base: main
Choose a base branch
from
+6 −0
Draft

Compose: Bridge for orgs #24056

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions content/manuals/compose/bridge/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down