Quickstart: Run a data plane in your VPC
This quickstart applies to the Enterprise plan, where the control plane runs in Postman cloud and you run the data plane in your own VPC. It strings together the minimum steps to get one data plane running: register it in the console, create its Secret, install the Helm chart, and confirm it serves traffic. Each step links to the page with the full details.
This quickstart uses the distributed secret store, so you don’t need a database. The gateway pods share the credentials the gateway stores among themselves, and each pod keeps its copy on its own volume. For the alternatives, see Choose a secret store.
Prerequisites
Before you begin, make sure you have the following:
- A Kubernetes cluster with egress to the control plane’s sync address. See Requirements and sizing and Network and egress.
kubectland Helm 3.- The Helm chart from Postman.
- These images, in a registry your cluster can pull from:
- The gateway image, from Postman.
ghcr.io/huggingface/text-embeddings-inference:cpu-1.9, the embedder for MCP tool search. When it starts, it downloads its model fromhuggingface.co. To run it without that access, see Run the tool-search embedder.
- A default StorageClass in the cluster. Each gateway pod gets its own 1 GiB volume.
- A NetworkPolicy controller, so that only gateway pods can reach the secret store’s ports. Without one, the chart’s NetworkPolicy has no effect.
- The Super admin role in the console, so you can open Admin > Gateway health.
Register the data plane in the console
The data plane enrolls with its own Kubernetes service account token, so there’s no token to mint or rotate.
-
Find your cluster’s OIDC issuer:
Copy the
issuervalue from the output. On EKS, you can also runaws eks describe-cluster --name <cluster> --query cluster.identity.oidc.issuer --output text. -
In the console, open Admin, select Gateway health, and then select Enroll data plane.
-
Select Workload attestation, and enter the following. The namespace, service account, and audience must match what you install later in this quickstart, so use these values exactly.
- Cluster OIDC issuer URL: the issuer from step 1.
- Namespace:
pm-fabric-dp. The quickstart installs the chart in this namespace. - Service account:
fabric-dp-sa. The chart names it after the Helm release,fabric-dp. - Audience:
fabric-cp. - Tenant ID: keep the prefilled value, and copy it for your values file.
-
Select Register anchor.
-
Copy the Sync endpoint, and select Download CA bundle. You need both for your values file.
After you register, the console also shows data plane configuration snippets. You don’t need to apply them, because attestation.enabled in your values file sets the same things.
If the control plane can’t reach your cluster’s issuer, for example on a private cluster, select Paste JWKS instead, and paste the output of kubectl get --raw /openid/v1/jwks. If you can’t use workload attestation, use a bootstrap token. See Connect to the control plane.
Create the namespace and Secret
FABRIC_GW_SECRET_KEY encrypts the credentials the gateway stores. If you lose it, the gateway can’t decrypt them. Store it in your secret manager, and then delete secret-key.txt. You generate the encryption key yourself. It doesn’t come from Postman. For every key and other ways to create the Secret, see Secrets and keys.
Write a values file
Save this as my-values.yaml, with your own values:
With the collector sidecar off, set all three exporters to none. Otherwise the gateway keeps trying to export to the missing sidecar, and Gateway health reports its telemetry export as degraded.
For telemetry, external URLs, and every other value, see Helm values.
Install the chart
Keep the release name fabric-dp, so the ServiceAccount is fabric-dp-sa and matches the anchor you registered.
Replace ./fabric-gateway-chart with the path to the chart Postman gave you. Helm starts the gateway pods, which enroll with the control plane and then receive your configuration.
Check that it’s running
-
Check that the gateway pods are running and ready:
Three pods appear,
fabric-gateway-chart-0throughfabric-gateway-chart-2. Each hasSTATUSRunningandREADY1/1. -
In the console, open Admin, and then select Gateway health. Your pods appear as nodes with the status Healthy.
-
Select a node. Under Config sync, check that it shows Connected and an Applied version above
v0. Until it does, the pod hasn’t received your configuration, and requests to it can return a503or a404.
If a pod restarts in a loop, see Troubleshoot enrollment.
Send a request
Connect a provider in the console. For the steps, see Quickstart: Send your first request on the hosted gateway. Then send a request through your data plane:
-
In a separate terminal, forward the gateway’s port. The command keeps running, so leave it open:
-
In the console, select Admin > Data plane, and set Base URL to
http://localhost:8080. Then copy your route’s path. -
Send this request:
A 200 OK with a chat completion confirms that your data plane carries traffic. To confirm that the data plane reports to the control plane, check that its node shows Healthy in Gateway health.
Next steps
- To let clients outside the cluster reach the gateway, see Expose the gateway.
- Before production traffic, work through the Production checklist.
- To set up monitoring, see Monitor the data plane.

