[clubanderson]

Closes #10559

Root cause

Pull-only clusters intentionally make buildSingleClusterHealth return errClusterPullOnly, after which the hub falls back to s.heartbeatHealth[clusterID]. The hub stores heartbeat health under the resolved registry/SaaS entry.ClusterID, but current vllm-d spokes were heartbeating without a cluster health report: the spoke only populated ClusterHealth when the HIVE_CLUSTER_ID environment variable was set, even though boot had already resolved the effective cluster ID from config or env into b.cfg.Hub.ClusterID.

Live evidence from the hub showed vllm-d spokes heartbeating every ~2 minutes, repeated pull-only cluster-health queries for vllm-d, and no cluster health: using heartbeat fallback / stored health for vllm-d in the sampled logs. The vllm-d kube context was not reachable from this workstation, matching the pull-only design.

Fix

• Collect spoke heartbeat cluster health whenever the resolved hub cluster ID is non-empty, not only when HIVE_CLUSTER_ID is present.
• Add structured status/note fields for per-cluster health states.
• Render pull-only clusters with no heartbeat health as a neutral informational state: pull-only · awaiting spoke heartbeat, including last registry heartbeat age when known.
• Mark stale heartbeat health with a warning status/note instead of treating the configured pull-only condition as a red hub query error.
• Added regression coverage for the spoke-side gate, pull-only awaiting-heartbeat state, and stale heartbeat conversion.

Validation

• gofmt -l on changed Go files
• git diff --check
• Per AGENTS.md, did not run local go test/go build; CI is the required verifier.

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign nicholasjackson for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

Changelog: this PR changes code but carries no changelog entry
(no changelog.d/ fragment and no CHANGELOG.md edit).

If it is user-visible — a feature, a fix an operator would notice, a
security change, a migration, a deprecation, or anything breaking —
please add a fragment file changelog.d/<category>-<pr-or-slug>.md
containing exactly your entry (see changelog.d/README.md; the
category is one of added/changed/deprecated/fixed/security). Please
do not append to CHANGELOG.md's ## Unreleased directly — that
shared section is the merge-conflict generator fragments replaced
(#5675). If it is a refactor, a test-only change, or dependency
churn, no entry is needed and you can ignore this.

This is a reminder, not a gate; it never blocks a merge.

[github-actions]

Open PR overlap check

Base branch: v5

Conflicts are checked with every PR merged onto the current tip of v5, so a PR that only needs a rebase is not reported as conflicting with its siblings.

PR	Title	Relation	Files
#10580	🐛 hub: pull-only clusters use heartbeat health; neutral awaiting-heartbeat state	CONFLICT	src/cmd/hive/main.go src/pkg/hub/assets/dashboard.html src/pkg/hub/saas_cluster_health.go
#10533	🐛 fix: refuse automated claims on needs-human issues	same files	src/cmd/hive/main.go
#10562	✨ hub dashboard: NPS feedback gets its own collapsible section above Users	same files	src/pkg/hub/assets/dashboard.html

[github-actions]

Thank you for your contribution! Your PR has been merged.

We'd love to hear how your experience was: share feedback