What Radar Shows
Control surface: Set image updates one or more regular or init-container images on the Rollout’s pod template or supportedworkloadRef target. Radar reads the current images before editing, rejects stale changes instead of overwriting them, and lets the Rollout controller start the resulting canary or blue-green rollout. A paused Rollout saves the template change but does not start rolling out until it is resumed. Promote, Promote full, Skip step, Retry, and Abort are also available on the Rollout detail page, each gated on a live capability probe (patch rollouts and patch rollouts/status are separate grants). Rollback goes through revision history, with an opt-in “skip canary steps” follow-up for hotfixes.
Rollout visibility: Radar keeps serving readiness separate from transient rollout activity. Resource tables, drawers, full workload views, and Applications show the active step, progress, pause, or failure without marking capacity served by the stable revision as unavailable.
Why it’s stuck: InconclusiveAnalysisRun names nothing on its own, so Radar resolves the AnalysisRun the controller recorded and surfaces the deciding metric - its success/failure condition, latest measured value, and message. The same verdict reaches AI agents through the Rollout’s issue field.
Topology: Rollout → active AnalysisRun (uses), labelled by trigger (step / background / pre-promotion / post-promotion). Only the runs the Rollout’s status points at are graphed - historical runs would grow the graph without bound.
Timeline: Step index, traffic weights, pause conditions, abort/promote-full, and stable-ReplicaSet moves are all recorded as distinct events; a Rollout sits in Progressing for the whole canary, so phase alone would show nothing.