DOCS-2884: Make Typha node-count guidance consistent - #2913
Merged
Conversation
The docs gave two different node counts for when Typha matters. The install and metrics pages say Typha applies above 50 nodes, while the Typha and architecture overview pages say it becomes essential at 100 or more nodes. A customer flagged the conflict. Remove the fixed "100+ node" figure from the Typha and architecture overview pages in Calico Open Source and Calico Enterprise, across the latest and all supported versioned docs. The operator always deploys and autoscales Typha, so a fixed node count does not apply there. The 50-node threshold stays on the manifest install and metrics pages, which is the only place a manual threshold is relevant. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✅ 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 Typha documentation across Calico Open Source and Calico Enterprise (current + supported versioned docs) to remove the fixed “100+ node” threshold and avoid conflicting scale guidance across pages.
Changes:
- Removed the “(100+ node)” qualifier from Typha “Advantages” text in Typha overview pages.
- Removed the same qualifier from the Typha section in architecture overview pages across OSS and Enterprise versioned docs.
Reviewed changes
Copilot reviewed 22 out of 22 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| calico/reference/typha/overview.mdx | Removes fixed “100+ node” wording from Typha advantages text. |
| calico/reference/architecture/overview.mdx | Removes fixed “100+ node” wording from Typha architecture section. |
| calico-enterprise/reference/component-resources/typha/overview.mdx | Removes fixed “100+ node” wording from Typha advantages text. |
| calico-enterprise/reference/architecture/overview.mdx | Removes fixed “100+ node” wording from Typha architecture section. |
| calico-enterprise_versioned_docs/version-3.24-1/reference/component-resources/typha/overview.mdx | Removes fixed “100+ node” wording from Typha advantages text (v3.24-1). |
| calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx | Removes fixed “100+ node” wording from Typha architecture section (v3.24-1). |
| calico-enterprise_versioned_docs/version-3.23-2/reference/component-resources/typha/overview.mdx | Removes fixed “100+ node” wording from Typha advantages text (v3.23-2). |
| calico-enterprise_versioned_docs/version-3.23-2/reference/architecture/overview.mdx | Removes fixed “100+ node” wording from Typha architecture section (v3.23-2). |
| calico-enterprise_versioned_docs/version-3.22-2/reference/component-resources/typha/overview.mdx | Removes fixed “100+ node” wording from Typha advantages text (v3.22-2). |
| calico-enterprise_versioned_docs/version-3.22-2/reference/architecture/overview.mdx | Removes fixed “100+ node” wording from Typha architecture section (v3.22-2). |
| calico-enterprise_versioned_docs/version-3.21-2/reference/component-resources/typha/overview.mdx | Removes fixed “100+ node” wording from Typha advantages text (v3.21-2). |
| calico-enterprise_versioned_docs/version-3.21-2/reference/architecture/overview.mdx | Removes fixed “100+ node” wording from Typha architecture section (v3.21-2). |
| calico-enterprise_versioned_docs/version-3.20-2/reference/component-resources/typha/overview.mdx | Removes fixed “100+ node” wording from Typha advantages text (v3.20-2). |
| calico-enterprise_versioned_docs/version-3.20-2/reference/architecture/overview.mdx | Removes fixed “100+ node” wording from Typha architecture section (v3.20-2). |
| calico_versioned_docs/version-3.32/reference/typha/overview.mdx | Removes fixed “100+ node” wording from Typha advantages text (v3.32). |
| calico_versioned_docs/version-3.32/reference/architecture/overview.mdx | Removes fixed “100+ node” wording from Typha architecture section (v3.32). |
| calico_versioned_docs/version-3.31/reference/typha/overview.mdx | Removes fixed “100+ node” wording from Typha advantages text (v3.31). |
| calico_versioned_docs/version-3.31/reference/architecture/overview.mdx | Removes fixed “100+ node” wording from Typha architecture section (v3.31). |
| calico_versioned_docs/version-3.30/reference/typha/overview.mdx | Removes fixed “100+ node” wording from Typha advantages text (v3.30). |
| calico_versioned_docs/version-3.30/reference/architecture/overview.mdx | Removes fixed “100+ node” wording from Typha architecture section (v3.30). |
| calico_versioned_docs/version-3.29/reference/typha/overview.mdx | Removes fixed “100+ node” wording from Typha advantages text (v3.29). |
| calico_versioned_docs/version-3.29/reference/architecture/overview.mdx | Removes fixed “100+ node” wording from Typha architecture section (v3.29). |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| - Since one Typha instance can support hundreds of Felix instances, it reduces the load on the datastore by a large factor. | ||
| - Since Typha can filter out updates that are not relevant to Felix, it also reduces Felix's CPU usage. In a high-scale (100+ node) Kubernetes cluster, this is essential because the number of updates generated by the API server scales with the number of nodes. | ||
| - Since Typha can filter out updates that are not relevant to Felix, it also reduces Felix's CPU usage. In a high-scale Kubernetes cluster, this is essential because the number of updates generated by the API server scales with the number of nodes. |
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 Calico docs gave two different node counts for when Typha matters. The install and metrics pages say Typha applies above 50 nodes, while the Typha and architecture overview pages say it becomes essential at 100 or more nodes. A customer flagged the conflict, and it was discussed in the #docs channel on 2026-03-18.
This change removes the fixed 100+ node figure from the Typha and architecture overview pages in Calico Open Source and Calico Enterprise, across the latest and all supported versioned docs. The operator always deploys and autoscales Typha, so a fixed node count does not apply there. The 50-node threshold stays on the manifest install and metrics pages, which is the only place a manual threshold is relevant.
Ticket: https://tigera.atlassian.net/browse/DOCS-2884
The same one-line edit is repeated across all product versions, so reviewers can check these representative pages:
I will add deploy preview links to these pages once the preview build finishes.