@@ -8,14 +8,17 @@ This section explains how to deploy MCP Gateway in various environments — from
8
8
9
9
MCP Gateway supports multiple deployment strategies:
10
10
11
- | Method | Description |
12
- | --------| -------------|
13
- | [ Local] ( local.md ) | Run directly on your dev machine using ` make ` or ` uvicorn ` |
14
- | [ Container] ( container.md ) | Package and run as a container using Docker or Podman |
15
- | [ Kubernetes / OpenShift] ( kubernetes.md ) | Deploy to any K8s-compliant platform using a Helm chart or manifests |
16
- | [ IBM Code Engine] ( ibm-code-engine.md ) | Run in serverless containers on IBM Cloud |
17
- | [ AWS] ( aws.md ) | Deploy to ECS, EKS, or EC2 instances |
18
- | [ Azure] ( azure.md ) | Run using Azure Container Apps, Web Apps, or AKS |
11
+ | Method | Description |
12
+ | ------------------------------------- | ----------------------------------------------------------------------------------------- |
13
+ | [ Local] ( local.md ) | Run directly on your dev machine using ` make ` , ` uvicorn ` , or a virtual-env |
14
+ | [ Container] ( container.md ) | Package and run as a single container image using Podman or Docker |
15
+ | [ Compose Stack] ( compose.md ) | Bring up Gateway + Postgres + Redis (and optional MPC servers) with Podman/Docker Compose |
16
+ | [ Minikube] ( minikube.md ) | Launch a local single-node Kubernetes cluster and deploy the Gateway stack |
17
+ | [ Kubernetes] ( kubernetes.md ) | Generic manifests or Helm chart for any K8s-compliant platform |
18
+ | [ OpenShift] ( openshift.md ) | OpenShift-specific deployment using Routes, SCCs, and Operator-managed back-ends |
19
+ | [ IBM Code Engine] ( ibm-code-engine.md ) | Serverless container build & run on IBM Cloud |
20
+ | [ AWS] ( aws.md ) | Deploy on ECS Fargate, EKS, or EC2-hosted containers |
21
+ | [ Azure] ( azure.md ) | Run on Azure Container Apps, App Service, or AKS |
19
22
20
23
---
21
24
0 commit comments