DOCS-3006: Point the CRD migration manifest link at the public OSS copy (stopgap) - #2914
Merged
Merged
Conversation
…py (stopgap) The DatastoreMigration CRD manifest is not published to downloads.tigera.io for the released Calico Enterprise versions, so step 2 of the CRD migration page returns 403 for users (DE-4494). The manifest is byte-identical across CE 3.23, CE 3.24, and open-source Calico 3.32.1 (same SHA-256), since it is controller-gen output from the shared kube-controllers source. Point the install command at the already-public open-source copy so the step works today. Revert to $[filesUrl]/manifests/ once DE-4494 publishes the CE artifact. Applied to version-3.23-2 (latest) and version-3.24-1, which are served in prod; next is left on $[filesUrl] because its publish is fixed by DE-4494 and a v3.32.1 pin would be wrong for a future release.
✅ 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 addresses a broken DatastoreMigration CRD install step in Calico Enterprise docs where the release-specific artifact on downloads.tigera.io returns 403. As a stopgap (tracked as DE-4494), it updates the two production-served versioned docs pages to reference the public OSS CRD manifest (Calico v3.32.1) and records a note to revert once the Enterprise artifact is published again.
Changes:
- Update CE 3.23-2 and 3.24-1 CRD migration docs to
kubectl applythe DatastoreMigration CRD from the publicprojectcalico/calicov3.32.1raw URL. - Add an inline MDX comment documenting the stopgap rationale and the intended revert target (
$[filesUrl]/manifests/...).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| calico-enterprise_versioned_docs/version-3.24-1/operations/crd-migration.mdx | Points DatastoreMigration CRD install step to public OSS manifest; adds stopgap note for later revert. |
| calico-enterprise_versioned_docs/version-3.23-2/operations/crd-migration.mdx | Same change as 3.24-1 for the latest prod-served CE version; adds stopgap note for later revert. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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 DatastoreMigration CRD manifest is not published to downloads.tigera.io for the released Calico Enterprise versions, so step 2 of the CRD migration page returns 403 for users. This is tracked with the Delivery Engineering team in DE-4494.
The manifest is byte-identical across CE 3.23, CE 3.24, and open-source Calico 3.32.1 (verified by SHA-256), because it is controller-gen output from the shared kube-controllers source. As a stopgap, this points the install command at the already-public open-source copy so the step works today. It should be reverted to $[filesUrl]/manifests/ once DE-4494 publishes the Calico Enterprise artifact. An MDX comment next to each command records this.
Applied to the two versions served in prod:
The next version is intentionally left on $[filesUrl], because DE-4494 fixes the master publish that feeds it, and pinning next to a v3.32.1 tag would be wrong for a future release.
The DOCS-2995 link-checker skip entry stays in place until the artifact is published and these links revert.
Reviewers can check the changed pages once the deploy preview builds:
https://tigera.atlassian.net/browse/DOCS-3006