DOCS-3062: Point the v3 CRD install commands at published manifests - #3048
Merged
Merged
Conversation
The page told readers to apply v3 CRDs from api/config/crd/ and the DatastoreMigration CRD from a path inside kube-controllers. Neither is published in the release, so both commands returned 404 and the install could not proceed. Both are in the manifests directory. The v3 CRD step also has to branch on the Kubernetes version, because the beta MutatingAdmissionPolicy API arrives in 1.36, which is what the native v3 CRDs page already documents.
❌ Deploy Preview for tigera failed. Why did it fail? →
|
✅ 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.
The on-premises install page pointed the v3 CRD and DatastoreMigration install commands at repository paths that are not published in the release, so both returned 404 and the install could not proceed.
The version branch matches what operations/native-v3-crds.mdx already documents: the beta MutatingAdmissionPolicy API arrives in Kubernetes 1.36.
Verified at the v3.33.0 tag: both old paths return 404, all three new ones return 200.