Skip to content

net: make summary-only routine status the default - #792

Closed
Patrick W. Healy (phealy) wants to merge 1 commit into
phealy/lightweight-status-viewer-detail-lifetimefrom
phealy/lightweight-status-default-summary
Closed

Patrick W. Healy (phealy) wants to merge 1 commit into
phealy/lightweight-status-viewer-detail-lifetimefrom
phealy/lightweight-status-default-summary

Conversation

@phealy

@phealy Patrick W. Healy (phealy) commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Purpose

Activate summary publication in runtime and rendered ConfigMap defaults after controller retention and client migrations. Retain explicit full mode for node-publishing rollback; bulk exports remain summary-only.

Compatibility

Based on #791. Upgrade controllers and bundled dashboard/CLI before agents. Settings are startup-only. Unsupported controller capability fails explicitly rather than silently enabling full streaming. Documentation covers TTL, leader-local state, pull-first fallback, and burst-memory limitations.

Validation

Full relevant Go race suites (status/config/node/controller/CLI), binary builds, scoped formatting/lint, and actual template rendering for default summary and explicit full override passed. Default-mode publisher tests cover HTTP/WebSocket summaries, resync, bootstrap recovery, and unsupported capability. Immediate-parent diff: 64 added+deleted lines.

Part of the draft lightweight-status stack based on #745. Summary default is now active at this layer.

Lightweight status draft stack

Base: #745. Each layer targets the preceding branch and remains draft.

#746 -> #747 -> #748 -> #750 -> #751 -> #752 -> #753 -> #754 -> #755 -> #756 -> #757 -> #758 -> #759 -> #760 -> #761 -> #762 -> #763 -> #764 -> #765 -> #766 -> #767 -> #768 -> #769 -> #770 -> #771 -> #772 -> #773 -> #774 -> #775 -> #776 -> #777 -> #778 -> #779 -> #780 -> #781 -> #782 -> #783 -> #784 -> #785 -> #786 -> #787 -> #788 -> #789 -> #790 -> #791 -> #792 -> #793 -> #794 -> #795 -> #796 -> #797 -> #798 -> #799

Activate summary in runtime and rendered ConfigMap defaults after controller retention and client migration. Keep explicit full publication rollback. Exercise default-mode HTTP/WebSocket publishers and document startup settings, controller-first rollout, TTL and fallback semantics.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d2243398-6c36-4c3d-969e-7ed7bfb5b459
This was referenced Sep 16, 2026
This was referenced Sep 16, 2026
@phealy

Copy link
Copy Markdown
Contributor Author

This PR was mistaken churn from splitting the lightweight-status work into unnecessarily small PRs. That was my mistake, not a requirement from the user.

Its changes are preserved in #748 within the user-approved, consolidated 12-PR draft stack. Closing this superseded PR; the implementation is not being discarded, and nothing has been merged into main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant