Use new crd.projectcalico.org.v1 Helm chart to install CRDs#2495
Use new crd.projectcalico.org.v1 Helm chart to install CRDs#2495caseydavenport wants to merge 1 commit intotigera:mainfrom
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. |
There was a problem hiding this comment.
Pull request overview
Updates the Helm-based installation guides to install Calico CRDs via the new crd.projectcalico.org.v1 Helm chart, instead of relying on the operator chart to install CRDs.
Changes:
- Split the OSS Helm install steps into (1) CRDs chart install, then (2) Tigera Operator chart install.
- Split the Calico Enterprise Helm install steps similarly, adding a CRDs chart install step before installing the operator.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| calico/getting-started/kubernetes/helm.mdx | Adds a dedicated Helm step to install CRDs from the new projectcalico/crd.projectcalico.org.v1 chart before installing the operator chart. |
| calico-enterprise/getting-started/install-on-clusters/kubernetes/helm.mdx | Adds a CRDs installation step ahead of the operator install for Enterprise Helm workflows. |
| 1. Create the necessary custom resource definitions. | ||
|
|
||
| ```bash | ||
| helm install calico-crds crd.projectcalico.org.v1-$[chart_version_name] --version $[releaseTitle] --namespace tigera-operator |
There was a problem hiding this comment.
The CRDs install command looks inconsistent with the rest of this page and likely won’t work as written: the chart reference crd.projectcalico.org.v1-$[chart_version_name] is neither repo-qualified (for tigera-ee/...) nor a local path (missing ./ and likely the .tgz filename produced by helm pull). Also, --namespace tigera-operator will fail unless the namespace already exists (this page currently only creates it later via --create-namespace on the operator install). Consider pulling the CRDs chart (like the operator chart) and installing from the local .tgz (or use a repo-qualified chart name), and add --create-namespace (or an explicit namespace creation step) before installing the CRDs release.
| helm install calico-crds crd.projectcalico.org.v1-$[chart_version_name] --version $[releaseTitle] --namespace tigera-operator | |
| helm install calico-crds tigera-ee/crds --version $[releaseTitle] --namespace tigera-operator --create-namespace |
| 1. Create the necessary custom resource definitions. | ||
|
|
There was a problem hiding this comment.
The earlier “Operator based installation” description still says the operator and CRDs are installed using a single Helm chart. With the new separate CRDs chart step, please update that text to reflect that CRDs are installed via the crd.projectcalico.org.v1 chart and the operator is installed via the tigera-operator chart, so the conceptual description matches the procedure.
| 1. Create the necessary custom resource definitions. | ||
|
|
There was a problem hiding this comment.
The “Operator based installation” concept section above still implies the operator and CRDs are installed using a single Helm chart. Since this procedure now installs CRDs via a separate crd.projectcalico.org.v1 chart before installing projectcalico/tigera-operator, please update that conceptual wording to match the new two-step flow to avoid confusing readers.
1 participant
Product Version(s):
Issue:
Documents projectcalico/calico#11727
Link to docs preview:
SME review:
DOCS review:
Additional information:
Merge checklist: