Add separate CRD chart to enterprise Helm install docs#2557
Merged
caseydavenport merged 2 commits intomainfrom Mar 3, 2026
Merged
Add separate CRD chart to enterprise Helm install docs#2557caseydavenport merged 2 commits intomainfrom
caseydavenport merged 2 commits intomainfrom
Conversation
The tigera-operator chart no longer bundles CRDs — they're now in a separate crd.projectcalico.org.v1 chart. This updates the enterprise Helm install docs to match the pattern already in place for open source Calico: download the CRD chart, install it before the operator. Covers standard install, management cluster, and managed cluster pages.
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!
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 updates the Calico Enterprise Helm installation documentation to include the separate crd.projectcalico.org.v1 chart that was split out from the tigera-operator chart (see referenced upstream PR #11727). The open source Calico docs already reflected this change, but the enterprise docs were missing the CRD chart download and install steps in several places.
Changes:
- Adds
helm pull tigera-ee/crd.projectcalico.org.v1download step to the standard enterprise Helm install, management cluster (both NodePort and LoadBalancer), and managed cluster docs. - Adds a new
helm install calico-crds crd.projectcalico.org.v1-$[chart_version_name].tgz --namespace tigera-operatorstep to all three multicluster Helm install docs. - Fixes the existing CRD install command in the standard enterprise doc by adding the missing
.tgzextension and removing an incorrect--versionflag (not applicable when installing from a local.tgzfile).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
calico-enterprise/getting-started/install-on-clusters/kubernetes/helm.mdx |
Adds missing helm pull for CRD chart; fixes existing CRD install command (.tgz extension, removes erroneous --version flag) |
calico-enterprise/multicluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx |
Adds CRD chart helm pull and CRD helm install steps for both NodePort and LoadBalancer tabs |
calico-enterprise/multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx |
Adds CRD chart helm pull and CRD helm install steps |
.../multicluster/set-up-multi-cluster-management/helm-install/create-a-managed-cluster-helm.mdx
Outdated
Show resolved
Hide resolved
calico-enterprise/getting-started/install-on-clusters/kubernetes/helm.mdx
Outdated
Show resolved
Hide resolved
...lticluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx
Outdated
Show resolved
Hide resolved
...lticluster/set-up-multi-cluster-management/helm-install/create-a-management-cluster-helm.mdx
Outdated
Show resolved
Hide resolved
ctauchen
reviewed
Mar 3, 2026
Collaborator
ctauchen
left a comment
ctauchen
left a comment
There was a problem hiding this comment.
Do the copilot comments merit attention? Otherwise LGTM. @caseydavenport
The CRD chart is installed first, so it needs to create the namespace. The operator install runs after, so the namespace already exists.
ctauchen
pushed a commit
to ctauchen/docs
that referenced
this pull request
Mar 4, 2026
ctauchen
pushed a commit
to ctauchen/docs
that referenced
this pull request
Mar 4, 2026
ctauchen
pushed a commit
to ctauchen/docs
that referenced
this pull request
Mar 4, 2026
ctauchen
pushed a commit
to ctauchen/docs
that referenced
this pull request
Mar 4, 2026
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
tigera-operatorchart no longer bundles CRDs (see projectcalico/calico#11727) — they're now in a separatecrd.projectcalico.org.v1chart. The open source Calico install docs already have this, but the enterprise install docs were still missing it in a few places.This adds the CRD chart download + install step to:
Also fixes the existing CRD install command in the standard enterprise doc (was missing
.tgzextension and had an unnecessary--versionflag for a local file).Fixes https://tigera.atlassian.net/browse/CORE-12418