kitchen-ops-bff/docs/runbooks/containerization.md

Containerization Runbook

Image Build

If the repo consumes internal packages from Gitea, pass feed credentials as build args.

docker build   --build-arg NUGET_FEED_USERNAME=<gitea-login>   --build-arg NUGET_FEED_TOKEN=<gitea-token>   -t agilewebs/kitchen-ops-bff:dev .

Local Run

docker run --rm -p 8080:8080 --name kitchen-ops-bff agilewebs/kitchen-ops-bff:dev

Health Probe

• Path: /health
• Fallback path: /healthz
• Port: 8080

Runtime Notes

• Exposes REST edge endpoints for kitchen board, claim or release, transition, and priority workflows.
• Requires KitchenService__BaseAddress to resolve the upstream kitchen-service runtime.
• Requires ThalosAuth__BaseAddress to resolve Thalos session introspection endpoint.
• Returns standardized auth failures (401|403|503) with x-correlation-id propagation.

Health Endpoint Consistency

• Canonical probe: /health
• Compatibility probe: /healthz
• Container port: 8080

Demo Integration

• Participates in: restaurant demo compose stack.
• Integration artifact path: greenfield/demo/restaurant/docker-compose.yml

Known Limitations

• Kitchen-ops now delegates dashboard and work-item actions to kitchen-service, which projects persisted kitchen ticket state and syncs order progression back into the shared restaurant lifecycle.
• Temporary edge-state translation remains in place for existing web clients until the Stage 47 kitchen web task adopts the canonical kitchen-service states directly.
• Demo PostgreSQL seeds validate integration contracts and smoke determinism, but do not yet imply full persistence implementation parity.