Security on INFINI Pizza

Security

Mon, 01 Jan 0001 00:00:00 +0000

Security #

Pizza ships an API-key based authentication and role model for the data plane and management APIs. It is off by default; the shipped pizza.yml enables it.

Enabling authentication #

security:
 auth_enabled: true
 # no bootstrap_key here — see below

With auth enabled, every data-plane and management request must carry a valid API key — Authorization: Bearer <key> or X-Api-Key: <key>. Unauthenticated requests are answered with 401 and a deliberately generic body. Anonymous operational-plane reads (console assets, readiness probes) stay open; mutating /_cluster and /_node management requires a key once auth is on.

Keystore

Mon, 01 Jan 0001 00:00:00 +0000

Keystore #

The keystore is a node-local file of secrets referenced from pizza.yml — API keys and tokens never have to live in the config file itself. Entries resolve through ${keystore:NAME} references:

node:
 embedding:
 endpoints:
 - name: openai
 url: https://api.openai.com/v1/embeddings
 api_key: ${keystore:openai}

The file is <config dir>/keystore.json — next to the config file it serves, so one instance per config (multi-instance hosts keep separate keystores) and it never enters the data directory’s lifecycle. It is written 0600 and replaced atomically; entries never enter cluster metadata, raft logs, or API responses — views answer with a masked hint only (sk-…4f2a).

Keystore hot-reload

Mon, 01 Jan 0001 00:00:00 +0000

Keystore hot-reload #

Rotating a secret no longer restarts the node. ${keystore:...} references re-resolve into the running configuration on demand: console edits trigger the reload themselves, and out-of-band changes (a CLI edit, a replaced mounted Secret) are one call away.

curl -X POST http://127.0.0.1:28000/_node/_local/keystore/_reload \
 -H 'Authorization: Bearer pz_bootstrap_key'

The answer says exactly what happened — key names only, values stay write-only:

{
 "entries": 3,
 "read_only": false,
 "references": 2,
 "changed": ["node.embedding.endpoints", "catalog.join_token"],
 "unchanged": 0,
 "failed": []
}

A rotated embedding API key applies to the next inference call; a rotated catalog.join_token to the next join attempt. A reference whose entry disappeared keeps its running value and lands in failed until the entry returns — reload never aborts the node the way a missing entry aborts boot.