Deploy the Passport Proxy
The Passport Proxy runs inside your cloud, where it resolves secret references from your secret store at request time. This is why Passport Cloud never handles your real secrets. For more information, see Passport Proxy.
This section covers a production deployment of the proxy in your Kubernetes environment. It starts with getting access to the Passport registry, then configuring and installing the proxy. By the end, you’ll have a running proxy that intercepts and logs API traffic and is ready to register with Passport Cloud.
This deployment process is only supported from macOS and Linux.
To try Passport on your own machine first, ask your coding agent to set up an evaluation proxy with the Passport plugin.
Prerequisites
Before you begin, make sure you have the following:
- macOS or Linux
- Docker installed and configured
- Helm 3.8 or later
openssl- Kubernetes 1.25 or later, with the following:
kubectlaccess and permission to create a namespace- An ingress controller
- Permission to create an internal load balancer
- A TLS certificate for the management hostname
- Access to edit DNS for two hostnames
What you’ll need
To deploy the Passport Proxy, you’ll work with the following:
Get registry access
The proxy image and Helm chart are served from the Passport registry, and you need a credential to pull them. Get registry access to generate a registry credential, pull the proxy image, and export the chart’s default values.
Configure the proxy
The proxy needs to know which organization it serves, have its own keys, and know where to find your credentials and send audit events before it can start. Configure the Passport Proxy to find your organization ID, generate the proxy’s keys, and set the values in values.yaml for your environment.
Install the proxy
Install the Passport Proxy with Helm to run it in your cluster, confirm that it’s running, and note the values you need to register it in Passport. This page also covers where to view logged API traffic.

