Skip to main content
The Infisical Gateway enables secure outbound-only communication between your private resources and the Infisical platform, without exposing inbound ports in your network. For a full overview of how gateways work, see the Gateway documentation.

Installation

1

Add the Helm repository

2

Install the chart

The enrollment token is single-use and expires in 1 hour. Persistent storage (enabled by default) is required so credentials survive pod restarts.
3

Verify the deployment

Uninstall

Configuration reference

Direct listen mode

By default the gateway connects out to a relay. To have Infisical connect to the gateway instead, set gateway.listenAddress to the address Infisical dials.
The chart takes the container port from gateway.listenAddress, points the Service at it, and exposes that same port, which keeps all three in step. A host:port value is required, and the chart fails the render if the port is missing. Set service.port only if you want the Service to answer on a different port than the gateway binds, in which case the listen address has to name the Service’s port. The Service is created only in direct listen mode. A relay-mode gateway accepts no connections and needs none. The address has to be one Infisical can resolve and reach. An in-cluster Service DNS name works when you self-host Infisical in the same cluster. From outside the cluster, expose the gateway through an Ingress or a LoadBalancer Service and register that address instead. Direct listen is only available on self-hosted Infisical.

Default Helm values