Spec reference
Firebolt Operator-owned fields on engine templates
The validating webhook rejects user input on paths the Firebolt Operator owns onspec.template (and the same rules apply to
FireboltEngineClass.spec.template when referenced).
Rejected on the pod template:
- StatefulSet-bound fields:
terminationGracePeriodSeconds,subdomain,hostname,restartPolicy,activeDeadlineSeconds. - Footgun fields:
hostNetwork,hostPID,hostIPC,shareProcessNamespace,hostUsers. - Pod-template metadata except
labelsandannotations. - Labels or annotations under the
firebolt.io/prefix.
containers[name=="engine"]:
name,command,args,ports, probes, reservedFIREBOLT_*env keys.restartPolicy,stdin,stdinOnce,tty.
image, imagePullPolicy, resources, env, envFrom, volumeMounts,
securityContext, lifecycle, workingDir, terminationMessagePath,
terminationMessagePolicy, volumeDevices, resizePolicy.
Sidecar containers (any name other than engine) and additional
initContainers pass through verbatim, with one restriction: they may not
mount the Secret-backed operator volumes (auth-admin, tls-engine,
auth-signing-<key-id>). The engine-config, data, and runtime volumes
are mountable — mounting data from an init container is the supported way to
prepare the data directory before the engine starts. See
FireboltEngineClass CRD reference for
the full class-side allowlist.
Engine phases
Conditions
Status properties
Short name:
fireng.