droboticflow/docs/release/recent-integration-components.md

2.9 KiB

Unified candidate component release plan

Status: local preparation only; no image upload, configuration change or deployment authorized by this document.

The candidate includes source admission, cohort dashboards, acceptance opinion forwarding and slice recovery. The API-only release path is insufficient for this candidate.

Component Required candidate Release mechanism
API and annotation processor Same immutable API image from the reviewed integration commit Existing scripts/release.py, processor before API
Annotation validator The same candidate API image, retaining its validator command, resources and parallelism Separate reviewed conditional image/build-marker update
Worker Immutable Worker image from the same source commit Separate reviewed conditional image/build-marker update
Orbbec normalizer Candidate operator-builtin-orbbec-data-normalize runtime containing the updated Python source Resolve the effective operator image override/base runner first; separately approve the exact image reference change

Before approval, capture actual cluster/context/namespace UID, deployment UID/resourceVersion, old/new image digests and build metadata for every affected component. Record effective normalizer image routing; rebuilding the generic runner is insufficient if an operator-specific image overrides it. No mutable tag, full manifest apply, resource adjustment, index or migration is included. The optional placement proposal and external player asset distribution remain disabled.

Proposed sequence for review: make the new validator available first, then use the supported release flow for processor and API. After all API replicas are verified on the candidate, enable acceptance forwarding tests only in explicitly approved synthetic production fixtures. Update the normalizer image routing and Worker as a separately reviewed intake transition; determine the handling of in-flight intake jobs before making that change. Do not silently restart, replay or replace existing customer jobs. Each separate change needs its own concrete before/after snapshot and approval; this draft cannot be executed as a deployment plan until those values and the intake transition are resolved.

Rollback must retain source admission fencing and readers for forwarded opinion origins. Returning to the previous API can make failed source tasks claimable and miscount forwarded opinions. Prepare a compatible rollback candidate, retain all validation/handling records, and obtain rollback authorization separately. Partial failures require read-only reconciliation before another action.

Production verification is read-only unless exact synthetic write scope is approved. Use status/summary APIs; frame-timeline GET can persist validation state and is not a read-only probe. Pod readiness does not establish task/media correctness or 120-person capacity. Full work, eight-hour soak and node failure remain unaccepted.