Skip to content
MAF Learning Hub
Advanced Govern Orchestrate Duration: 30 min

Deploying agents on CloudHub 2.0

A designed agent network only delivers value once it is running - and running governed. This lesson covers deploying agents on CloudHub 2.0 with the Omni Gateway in front, so every request at runtime inherits the controls you defined in Track 3.

What you will learn

  • Where agents run in the MuleSoft runtime plane.
  • Why the Omni Gateway fronts deployed agents.
  • How a deployment is described and promoted across environments.

The runtime plane

CloudHub 2.0 is MuleSoft’s managed, containerized runtime for deploying applications and agents at scale (CloudHub 2.0). Deploying your agents there gives you elastic capacity, isolated replicas, and environment separation (sandbox to production).

Governed by the Omni Gateway

Placing the Omni Gateway in front of deployed agents means A2A and MCP traffic passes through your policy control point at runtime - the same governance you configured in Track 3 now applies in motion (Securing Agent Interactions with Omni Gateway).

Design-time meets runtime

Track 3 attached policies to cataloged assets; deployment is where those policies start enforcing real traffic. Discover -> Govern -> deploy is one continuous chain.

Describing a deployment

Deployments are declarative so they can be reviewed and promoted across environments:

# deployment.yaml (excerpt)
application:
  name: enterprise-broker
  target: cloudhub-2
  replicas: 2
  env: production
gateway:
  omni: true            # front the app with the Omni Gateway
  policies: [mcp-abac, rate-limiting]

Forward-looking

The deployment descriptor above is illustrative; confirm the exact CloudHub 2.0 and Omni Gateway deployment schema against current official documentation before use.

Next steps

Continue to Connectors and MCP tool binding to give your deployed agents safe, reusable access to enterprise systems.

References