Installation
1
Add the Helm repository
2
Install the chart
- Token Auth
- AWS Auth
- Kubernetes Auth
3
Verify the deployment
Uninstall
Configuration reference
Resource limits
PAM is heavier per session, so raise the chart’s resource limits:persistence.size above its 5Gi default if your sessions are long or numerous.
Direct listen mode
By default the gateway connects out to a relay. To have Infisical connect to the gateway instead, setgateway.listenAddress to the address Infisical dials.
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
values.yaml
values.yaml