DOCS-2995: Fix version and manifest URL errors on CRD migration page for latest - #2910
Merged
Merged
Conversation
…for latest Correct the Before you begin prerequisite to Calico Enterprise v3.23+, and replace the undefined manifestsUrl variable with filesUrl so the manifest URLs resolve. These fixes were already made in the current and 3.24 docs but were not backported to the 3.23 version served at latest.
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR backports two documentation fixes to the Calico Enterprise v3.23 (latest-served) CRD migration page so the prerequisites and manifest download URLs render correctly for readers.
Changes:
- Corrects the “Before you begin” prerequisite from v3.32+ to v3.23+.
- Fixes broken manifest URLs by replacing the undefined
$[manifestsUrl]variable with the correct$[filesUrl]variable.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…ifest The corrected filesUrl link on the CRD migration page now resolves to a real downloads.tigera.io URL, but the DatastoreMigration CRD manifest is not yet published for any released version, so the link checker fails the build on a 403. Skip this manifest in the crawler until the publish step from calico-private master is cut into a release. The v3.23.1 and v3.24.0-1.0 artifacts are both absent today, so the skip is version agnostic.
LinkedIn returns 999 to datacenter crawlers, so the Project Calico company page fails the build link check even though it loads fine in a browser. This is a pre-existing dead link on the latest about and product-editions pages, unrelated to the CRD migration fix, but it blocks CI on this branch. Skip it the same way the Tigera LinkedIn page is already skipped.
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.
The CRD migration page for Calico Enterprise latest (version 3.23) has two errors reported in Slack.
Both fixes already landed in the current and 3.24 docs (#2907) but were not backported to the 3.23 version served at latest.
Two follow-on commits keep the build link checker green:
Reviewers can check the changed page once the deploy preview builds:
https://tigera.atlassian.net/browse/DOCS-2995