Before you start
- Use a stable HTTPS site URL; complete administrator setup
- encryption-key must be 32 hexadecimal characters; back it up securely
- database-url must target db:5432/app; redis-url must target redis:6379 with matching passwords
- Back up PostgreSQL and encryption keys together
- This is the Infisical server; Hakopod's optional operator integration is configured separately
- After deployment, open Custom domains, verify the site URL hostname, and apply routing and TLS before using login or callbacks
Configuration that needs your attention
This preset includes the Infisical server, PostgreSQL and Redis. It does not configure the optional Hakopod operator integration.
Use a stable HTTPS origin. The standard non-FIPS encryption key is 32 hexadecimal characters; the authentication secret is 32 random bytes encoded as Base64.
Database and Redis URLs must match their saved credentials and target db:5432/app and redis:6379. Retain encryption keys with database backups.
Required secrets
Configure these scoped secrets during deployment review in your Hakopod installation. Secret values stay out of the application TOML.
-
auth-secret -
database-password -
database-url -
encryption-key -
redis-password -
redis-url
This preset needs a public site URL. Set the correct origin before starting the application.
Use this preset
- Open the Catalog in your own Hakopod dashboard and select Infisical.
- Choose the project, environment, and application name. Set the required values and secret references.
- Review the generated configuration, resource requests, networking, and storage plan.
- Deploy, then inspect readiness and logs. Configure backups for persistent data before relying on the service.
Read the upstream setup documentation ↗
View native TOML and setup notes ↗
Pinned container image
docker.io/infisical/infisical:v0.165.10@sha256:204bd63c7a281d9157752ce0bf8d506e7380cac5a0665324eeab8d580b069266
The catalog pins this image for reproducibility. Review upstream updates and compatibility before changing it.