Show in-cluster Radar upgrade status - #1535
Conversation
|
bugbot run verbose=true |
|
Bugbot request id: serverGenReqId_cf65f3da-96ea-4e27-b54b-1a96e6c19891 |
Bugbot rules debugNo rules were used for this review. https://cursor.com/docs/bugbot#team-rules Bugbot request id: serverGenReqId_cf65f3da-96ea-4e27-b54b-1a96e6c19891 |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 9671e6f. Configure here.
|
bugbot run verbose=true |
|
Bugbot request id: serverGenReqId_5f954a7e-c60d-42f9-8e03-db877f9a0ecc |
Bugbot rules debugNo rules were used for this review. https://cursor.com/docs/bugbot#team-rules Bugbot request id: serverGenReqId_5f954a7e-c60d-42f9-8e03-db877f9a0ecc |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit ba9f4e7. Configure here.
…-update-checks # Conflicts: # internal/server/server.go
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit e45f0d0. Configure here.
| error?: string; | ||
| } | ||
|
|
||
| const UPDATE_CHECK_STORAGE_KEY_PREFIX = 'radar-update-check' |

Summary
Shows standalone in-cluster operators which Radar version is running, whether a newer release is available, and where to make the upgrade in Helm-, Argo CD-, or Flux-managed installations. When ownership cannot be verified, Radar links to safe installation-specific guidance instead of guessing.
What changed
In-cluster upgrade experience
Update checks
Testing
make tscmake testmake buildDeployment note
Deploy the paired receiver change before releasing this Radar change: https://github.com/skyhook-dev/marketing/pull/284
Note
Medium Risk
Changes outbound update telemetry classification and adds a new browser-triggered relay path, but scope is bounded (daily, in-cluster-only) and upgrade handoffs avoid acting on unverified GitOps ownership.
Overview
Standalone in-cluster Radar now surfaces the running version on Home, highlights available upgrades by gap (patch / minor / stale major), and routes operators to the right next step instead of a generic release popup.
Upgrade UX: The floating update banner is hidden for in-cluster and Cloud viewers; local/desktop behavior stays the same. Verified Helm releases and GitOps controllers (via new
controllerRefon connect-self) can deep-link into the app; unknown or suspected ownership falls back to the expanded in-cluster upgrade docs (Helm, Argo CD, Flux, verify/rollback). Settings upgrade links point at those docs for in-cluster mode.Update checks: Backend checks are keyed by source (
release-onlyvs metered), single-flight cached, and tagged with build channel plus install timestamp when known. Development-shaped builds skip metered/browser relay traffic; Cloud/version-checkuses release-only lookup. In-cluster browsers trigger one best-effort dailyPOST /version-check/browserrelay (browser-proxy) that does not share the release-response cache with the normal check.Reviewed by Cursor Bugbot for commit 2edc412. Bugbot is set up for automated code reviews on this repo. Configure here.