Skip to content

Conversation

@caseydavenport
Copy link
Member

Product Version(s):

Issue:

Documents projectcalico/calico#11727

Link to docs preview:

SME review:

  • An SME has approved this change.

DOCS review:

  • A member of the docs team has approved this change.

Additional information:

Merge checklist:

  • Deploy preview inspected wherever changes were made
  • Build completed successfully
  • Test have passed

Copilot AI review requested due to automatic review settings January 29, 2026 22:14
@caseydavenport caseydavenport requested a review from a team as a code owner January 29, 2026 22:14
@netlify
Copy link

netlify bot commented Jan 29, 2026

Deploy Preview for calico-docs-preview-next ready!

Name Link
🔨 Latest commit af7c772
🔍 Latest deploy log https://app.netlify.com/projects/calico-docs-preview-next/deploys/697bdbaf82d013000839cdc1
😎 Deploy Preview https://deploy-preview-2495--calico-docs-preview-next.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Jan 29, 2026

Deploy Preview succeeded!

Built without sensitive environment variables

Name Link
🔨 Latest commit af7c772
🔍 Latest deploy log https://app.netlify.com/projects/tigera/deploys/697bdbaf4842cd00082fb5f7
😎 Deploy Preview https://deploy-preview-2495--tigera.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 67 (🔴 down 1 from production)
Accessibility: 98 (no change from production)
Best Practices: 92 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

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
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.
Comment on lines +95 to +96
1. Create the necessary custom resource definitions.

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.
Comment on lines +82 to +83
1. Create the necessary custom resource definitions.

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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant