Document registry egress summary on the Image Registries page#4299
Merged
Conversation
The registry egress summary card was buried in a single sentence inside the "View pull activity" section with no heading, making it invisible in the page TOC. Give it a dedicated "View registry egress" section that describes the Team total / Proxy registry / Replicated registry / This app breakdown, and cross-link between pull activity, egress, and the related Egress Threshold Reached notification event. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
type::docs
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a dedicated View registry egress section to the packaging-private-images page and cross-links it with pull activity and the related alerting event.
Why
The registry egress summary card (shipped in vandoor #10046, made unconditional in #10118) was documented as a single sentence buried inside the View pull activity section, with no heading of its own. That left it invisible in the page's right-hand table of contents, so vendors landing on the page had no easy way to discover it. Even someone familiar with the page missed it.
Changes
## View registry egressH2 (its own TOC entry + stable#view-registry-egressanchor) describing the Registry egress this month summary and its Team total / Proxy registry / Replicated registry / This app breakdown.:::note).Follow-up
No screenshot exists for the egress summary card yet. I intentionally did not insert a broken image link; a
proxy-registry-registry-egress-summary.pngcan be added in a follow-up.🤖 Generated with Claude Code