EV-6817: Revert license-monitoring docs to license-agent model for 3.23#2852
Open
rene-dekker wants to merge 1 commit into
Open
EV-6817: Revert license-monitoring docs to license-agent model for 3.23#2852rene-dekker wants to merge 1 commit into
rene-dekker wants to merge 1 commit into
Conversation
The operator license-metrics feature (and license-agent removal) was meant for v3.24+, but leaked into the published 3.23 (version-3.23-2) snapshot via tigera#2629. This restores the license-agent model for 3.23 while keeping the DOCS-2919 FAQ improvements and leaving next (3.24+) intact. - Restore monitor/metrics/license-agent.mdx; delete operator-metrics.mdx - license-options.mdx: revert License metrics section to license-agent model, keep FAQ / grace-period / read-only expiry table - byo-prometheus.mdx: drop operator tab (unpublished manifest) - comms/index.mdx: remove dead link to deleted operator-metrics page - index.mdx + sidebar: restore license-agent entry - linkChecker.js: drop temporary 3.23.1 manifest skip Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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.

Summary
The operator license-metrics feature (and removal of the license-agent page) was intended for v3.24+, but leaked into the published 3.23 (
version-3.23-2) docs via #2629. A customer upgrading CE 3.22.6 → 3.23.1 hit this: the 3.23 docs no longer document the license-agent and point to an operator-metrics endpoint/manifest that isn't in 3.23 (operator-metrics-service-monitor.yamlis not published for any 3.23.x patch).This reverts the license-monitoring changes only in the
version-3.23-2snapshot, keeping the DOCS-2919 FAQ improvements and leavingnext(3.24+) untouched.Changes (version-3.23-2 only)
monitor/metrics/license-agent.mdx; deleteoperator-metrics.mdxlicense-options.mdx: revert the "License metrics" section to the license-agent model; keep the FAQ / grace-period / read-only expiry tablebyo-prometheus.mdx: drop the "operator" tab (applied the unpublished manifest)comms/index.mdx: remove the dead link to the deleted operator-metrics page (TLS-consolidation otherwise kept)operations/index.mdx+ sidebar: restore thelicense-agententrysrc/utils/linkChecker.js: drop the temporary 3.23.1 manifest skip (no longer referenced)Verification
docusaurus build(published versions incl. 3.23-2) passes with noonBrokenLinkserrorsnext(3.24+) unchanged — operator-metrics intact therelicenseagent.yamlconfirmed present on the download server for 3.23.1Ref: EV-6817 · Slack thread
🤖 Generated with Claude Code