Deploy Agent Network Instances
Deploy your agent network instance to a CloudHub 2.0 shared space or a CloudHub 2.0 private space. Agent network deployments are available on US Cloud and EU Cloud hosts only. For more information, see Control Plane Hosting Options.
Additionally, agent brokers follow the same monthly patching cadence as CloudHub 2.0. For the update schedule, see MuleSoft Commercial Cloud Schedule.
Agent Network Deployments and Omni Gateway
When you deploy, Omni Gateway secures inbound traffic to your agent network and outbound traffic from your brokers, agents, and MCP servers.
Omni Gateway applies these policies automatically at deployment.
| Agent Type | Policy |
|---|---|
Broker |
|
Agent (ingress and egress) |
|
MCP Server (ingress and egress) |
|
Last-Mile Security Considerations for Agent Networks
Agent networks in version 2.0 don’t support Last-Mile Security for outbound (egress) traffic on the Omni Gateway. If you have enabled Last-Mile Security, the agent network deploys and the broker can answer general questions, but it can’t route requests to downstream agents or MCP servers.
Agent networks route outbound traffic through the egress gateway (on port 8082, cluster endpoint). Last-Mile Security enforces TLS on the ingress-gateway-to-pod hop. The outbound path bypasses this hop, so the connections can’t be established.
If your deployment requires Last-Mile Security for other applications, deploy your agent network to a separate egress gateway that has Last-Mile Security disabled.
The broker’s egressgw.url resolving to the cluster endpoint is expected behavior, regardless of the Last-Mile Security setting.
Before You Begin
Make sure you review the prerequisites.
|
Redeploying an agent network to a different target or gateway (for example, switching between a shared space and a private space, or changing to a different gateway) is not supported and fails with a Runtime Manager error. To deploy to a different target or gateway, first manually delete the existing Runtime Manager application, then redeploy. |
When you deploy your agent network, the system deploys one instance for each connection defined in your agent network. If your agent network contains brokers, the system deploys one instance per broker.
Deploy Your Network Using MuleSoft Vibes
Use MuleSoft Vibes to deploy your agent network instances. For more information, see Creating API Specs with MuleSoft Vibes.
-
In the Anypoint Code Builder activity bar, click the agent icon
. -
Tell the agent that you want to deploy your agent network. MuleSoft Vibes does the rest.
To get started, try one of these suggested messages.
-
Deploy my agent network project to the production environment.
-
Deploy the hello-world-network project to staging.
-
Deploy agent network project at /path/to/project to dev environment with specific gateways.
-
Deploy my agent network to CloudHub 2.0.
Deploy Your Network Using Anypoint Code Builder
Deploy your agent network instance to a CloudHub 2.0 space directly from Anypoint Code Builder.
-
If you’re not logged in already, log in to your Anypoint Platform account.
-
In Anypoint Code Builder, choose one of the following:
-
In Explorer, right-click a project file and select Deploy Agent Network.
-
From the Command Palette, run this command: MuleSoft: Deploy Agent Network.
-
In Deploy Agent Network, specify the environment, target space, gateways, and other deployment information. If you don’t see any deployment targets to select, then you need to set up your target deployment space and set up gateways. For instructions, see Get Started with Agent Networks.
-
Select Deploy.
-
Your instances are now deployed and ready to test. The system deploys one instance for each connection defined in your agent network. If your agent network contains brokers, the system deploys one instance per broker.
Next, discover your agent network assets in Agents & Tools in Exchange, view your agent network in Agent Visualizer, apply a governance policy in API Manager, or monitor your agent network activity in Anypoint Monitoring.
Deploy a Network Using the Anypoint CLI
If you run operations within a CI/CD environment, use Anypoint CLI’s plugin to set up, create, build, publish, and deploy agent networks. For more information, see Build Agent Networks in a CI/CD Environment.
Resolve Agent Network Deployment Errors in Anypoint Code Builder
If you try to deploy an agent network project and see errors related to CLI version, install the latest Anypoint Code Builder version (1.24.1 or later) and then rebuild, republish, and deploy your project.
If you try to deploy an agent network project and see errors related to invalid API metadata, use API Manager to delete existing API instances that were created with previous a Anypoint Code Builder version. Then rebuild, republish, and deploy your project.