Skip to content

Use new crd.projectcalico.org.v1 Helm chart to install CRDs #2495

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
caseydavenport wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Use new crd.projectcalico.org.v1 Helm chart to install CRDs #2495

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion calico-enterprise/getting-started/install-on-clusters/kubernetes/helm.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,13 @@ To install a standard $[prodname] cluster with Helm:
}
</CodeBlock>

1. Install the Tigera Operator and custom resource definitions using the Helm 3 chart:
1. Create the necessary custom resource definitions.

Comment on lines +95 to +96
Copy link

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.
```bash
helm install calico-crds crd.projectcalico.org.v1-$[chart_version_name] --version $[releaseTitle] --namespace tigera-operator
Copy link

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Suggested change
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

Copilot uses AI. Check for mistakes.
```

1. Install the Tigera Operator using the Helm 3 chart:

```bash
helm install $[prodnamedash] tigera-operator-$[chart_version_name].tgz \
Expand Down
8 changes: 7 additions & 1 deletion calico/getting-started/kubernetes/helm.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,13 @@ For more information about configurable options via `values.yaml` please see [He
kubectl create namespace tigera-operator
```

1. Install the Tigera Operator and custom resource definitions using the Helm chart:
1. Create the necessary custom resource definitions.

Comment on lines +82 to +83
Copy link

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.
```bash
helm install calico-crds projectcalico/crd.projectcalico.org.v1 --version $[releaseTitle] --namespace tigera-operator
```

1. Install the Tigera Operator using the Helm chart:

```bash
helm install $[prodnamedash] projectcalico/tigera-operator --version $[releaseTitle] --namespace tigera-operator
Expand Down
Loading