Fix Enterprise CRD manifest references for native v3 CRD mode - #2882
Merged
caseydavenport merged 2 commits intoJul 29, 2026
Conversation
✅ 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
Updates Calico Enterprise installation/upgrade documentation to avoid breaking clusters that run in native projectcalico.org/v3 CRD mode by making the v1 vs v3 CRD bundle choice explicit, and by aligning Enterprise docs with Enterprise download locations/artifact names.
Changes:
- Replace legacy
operator-crds.yamlreferences withv1_crd_projectcalico_org.yamlacross multiple install paths/components. - Add an explicit warning to Helm upgrade guides explaining when to apply
v3_projectcalico_org.yamland how to detect native-v3 mode. - Fix Enterprise native-v3 CRD docs to use Enterprise chart/manifests download locations and reintroduce pull-secret/license steps.
Reviewed changes
Copilot reviewed 17 out of 17 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| calico-enterprise/operations/nftables.mdx | Updates CRD bundle reference to the explicit v1 manifest name. |
| calico-enterprise/operations/native-v3-crds.mdx | Switches Helm instructions to Enterprise chart downloads and adds pull-secret/license steps; fixes manifests URL to $[filesUrl]. |
| calico-enterprise/operations/crd-migration.mdx | Updates manifests URLs and adjusts stated minimum Enterprise version for the migration controller. |
| calico-enterprise/installation/install-calico-enterprise-mke-4k.mdx | Updates CRD bundle reference to the explicit v1 manifest name. |
| calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx | Uses explicit v1 CRD bundle name and adds warning/diagnostic for native v3 CRD clusters. |
| calico-enterprise/getting-started/upgrading/upgrading-calico-to-calico-enterprise/upgrade-to-tsee/helm.mdx | Uses explicit v1 CRD bundle name and adds warning/diagnostic for native v3 CRD clusters. |
| calico-enterprise/getting-started/install-on-clusters/windows-calico/rancher.mdx | Updates CRD bundle reference to the explicit v1 manifest name. |
| calico-enterprise/getting-started/install-on-clusters/rke2.mdx | Updates CRD bundle reference to the explicit v1 manifest name. |
| calico-enterprise/getting-started/install-on-clusters/rancher.mdx | Updates CRD bundle reference to the explicit v1 manifest name. |
| calico-enterprise/getting-started/install-on-clusters/kubernetes/quickstart.mdx | Updates CRD bundle reference to the explicit v1 manifest name. |
| calico-enterprise/getting-started/install-on-clusters/docker-enterprise.mdx | Updates CRD bundle reference to the explicit v1 manifest name. |
| calico-enterprise/_includes/components/InstallOpenShiftHCPResources.js | Updates CRD bundle reference in rendered OpenShift command snippet. |
| calico-enterprise/_includes/components/InstallOpenShift.js | Updates CRD bundle reference in rendered OpenShift command snippet. |
| calico-enterprise/_includes/components/InstallGKE.js | Updates CRD bundle reference in rendered install snippet. |
| calico-enterprise/_includes/components/InstallGeneric.js | Updates CRD bundle reference in rendered install snippet. |
| calico-enterprise/_includes/components/InstallEKS.js | Updates CRD bundle reference in rendered install snippets. |
| calico-enterprise/_includes/components/InstallAKS.js | Updates CRD bundle reference in rendered install snippets. |
Comments suppressed due to low confidence (1)
calico-enterprise/operations/native-v3-crds.mdx:157
- Same as above: this license install step uses
kubectl apply, but the rest of the Enterprise docs typically usekubectl createfor the initial license install. Aligning the verb improves consistency across guides.
kubectl apply -f </path/to/license.yaml>
ctauchen
approved these changes
Jul 29, 2026
Collaborator
|
LGTM, but needs rebase and merge conflict fixing. |
The two manifests are identical. The v1 name says which CRD group it installs, and matches what the open source docs already use.
The v3 CRD and DatastoreMigration manifests are published under downloads.tigera.io/ee, and the migration controller ships in Enterprise v3.23.
caseydavenport
force-pushed
the
casey-v3-crd-manifests
branch
from
July 29, 2026 14:24
de4b638 to
7d6b1ba
Compare
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.
Product Version(s): Calico Enterprise master
#2805 landed most of what this PR was doing. What's left are the manifest names and hosts it didn't touch.
operator-crds.yamlis a legacy alias forv1_crd_projectcalico_org.yaml. The two are byte-identical in calico-private, and the open source docs already use the v1 name. Renamed in the three remaining spots: the aggregation API server tab of both Helm upgrade pages, and the API server mode section of the native v3 CRDs page. Left the archive page and the ingress gateway canary tutorial alone, since those point at older artifacts that really are namedoperator-crds.yaml.The managed cloud install includes (AKS, EKS, GKE, Generic, OpenShift) get the same rename. They still install the v1 bundle, which is now inconsistent with v3 being the default for new installs, but that's a behavior change rather than a naming fix so I've left it out of this PR.
The Enterprise CRD migration guide was copied from open source and pointed at
$[manifestsUrl](docs.tigera.io) rather than$[filesUrl](downloads.tigera.io/ee), and claimed v3.32 as the version floor.Not fixed here, filed separately as https://tigera.atlassian.net/browse/CORE-13214:
migration.projectcalico.org_datastoremigrations.yamlis not published in any release artifact, so step 2 of the migration guide is a 404 in both products. That needs a build change, not a docs change.Link to docs preview:
SME review:
DOCS review: