Skip to main content

Spec reference

Firebolt Operator-owned fields on engine templates

The validating webhook rejects user input on paths the Firebolt Operator owns on spec.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 labels and annotations.
  • Labels or annotations under the firebolt.io/ prefix.
Rejected on containers[name=="engine"]:
  • name, command, args, ports, probes, reserved FIREBOLT_* env keys.
  • restartPolicy, stdin, stdinOnce, tty.
Allowed on the engine container (engine template wins over class): 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. See FireboltEngineClass CRD reference for the full class-side allowlist.

Engine phases

Conditions

Status properties

Short name: fireng.