Deployment
Requirements and steps to deploy InfraKitchen.
Requirements
To successfully deploy InfraKitchen, ensure that your system meets the following minimum requirements:
- Python: Version 3.14
- Node.js: Version 24
- PostgreSQL: Version 17
- Nginx: Version 1.28
- OpenTofu/Terraform: Version 1.10
- Yarn: Version 1.22
- Git Client: Latest stable version
Container Image
InfraKitchen provides a multi-stage Containerfile that builds the backend (Python + OpenTofu/Terraform + AWS CLI) and the frontend (Node.js), and serves the UI through the bundled Nginx.
The example file also references the Nginx configs and entrypoint script shipped in the same directory:
docs/examples/podman/Containerfiledocs/examples/podman/nginx.confdocs/examples/podman/websocket-map.confdocs/examples/podman/entrypoint.sh
To build the container image, run the following command from the root directory of the project:
podman build -f docs/examples/podman/Containerfile -t your-image-name:tag .
Kubernetes
InfraKitchen provides an example manifest: docs/examples/podman/k8s-manifest.yaml.
It contains an Nginx Ingress, a Service, and backend, scheduler, and worker Deployments, wired to PostgreSQL:
Use it directly, or as a base for your own manifest.
Prepare the manifest
Replace the placeholders <SERVICE_ACCOUNT_NAME>, <IMG_NAME>, <POSTGRES_HOST> and <HOST_NAME> with your actual values. Feel free to choose a Service Account name as you wish, for example infrakitchen-sa, it will be created when applying the manifest.
Create the namespace and switch context
Skip the first command if the namespace already exists.
kubectl create namespace infrakitchen
kubectl config set-context --current --namespace=infrakitchenGenerate secrets for JWT and encryption keys
The following command generates the two secret values the platform needs — an
ENCRYPTION_KEY for encrypting stored secrets and a JWT_KEY for signing
authentication tokens:
python server/generate_encryption_key.pyThe API refuses to start when JWT_KEY is missing, shorter than 32
characters, or one of the published placeholders (CHANGE_ME, supersecret).
Rerunning the script produces fresh values you can use to rotate the keys.
Note that rotating the ENCRYPTION_KEY invalidates everything encrypted with
the previous one (e.g. stored integration credentials), so plan the rotation
accordingly.
Create the secret
Create the secret with the two values generated in the previous step and your PostgreSQL password:
kubectl create secret generic infrakitchen-secrets \
--from-literal="enc-secret=<ENCRYPTION_KEY generated in the previous step>" \
--from-literal="jwt-secret=<JWT_KEY generated in the previous step>" \
--from-literal="postgres-password=<password of the PostgreSQL infrakitchen user>"Apply the manifest
The manifest references the secret created in the previous step:
kubectl apply -f docs/examples/podman/k8s-manifest.yamlThe UI and API are served from one origin through nginx, so the API sends no
CORS headers. To let another browser origin call the API, set
CORS_ALLOW_ORIGINS to a comma-separated list of exact origins (e.g.
https://portal.example.com). When INFRAKITCHEN_URL starts with https://,
the API also sends Strict-Transport-Security.