Repository navigation
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. |
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Resolve remaining documentation inconsistencies around overlap status terminology and version-specific behavior.
3 open findings
What changed in this PR
Updates Calico IPPool reference documentation across current, 3.33, 3.32, and 3.31.
Changes:
- Corrects field constraints, types, selectors, and allocation rules.
- Clarifies networking, NAT, and annotation behavior.
- Documents version-specific CIDR overlap handling and status conditions.
| File | Summary |
|---|---|
calico/reference/resources/ippool.mdx |
Updates current IPPool reference. |
calico_versioned_docs/version-3.33/reference/resources/ippool.mdx |
Updates 3.33 IPPool reference. |
calico_versioned_docs/version-3.32/reference/resources/ippool.mdx |
Updates 3.32 IPPool reference. |
calico_versioned_docs/version-3.31/reference/resources/ippool.mdx |
Updates 3.31 IPPool reference. |
🧠 Review effort: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| In API server mode, creating an IPPool with a CIDR that overlaps an existing pool is rejected synchronously at creation time. | ||
|
|
||
| When using [native v3 CRDs](../../operations/native-v3-crds.mdx), CIDR overlap validation is **asynchronous**. Pools with overlapping CIDRs are created successfully but receive a `Disabled` status condition. IPAM does not allocate addresses from disabled pools. Check the IPPool status to identify any pools that have been disabled due to CIDR overlap. | ||
| When using [native v3 CRDs](../../operations/native-v3-crds.mdx), CIDR overlap validation for pools created with `kubectl` is **asynchronous**. Pools with overlapping CIDRs are created successfully but receive an `Allocatable` status condition set to `False` with reason `CIDROverlap`. IPAM does not allocate addresses from disabled pools. Check the IPPool status to identify any pools that have been disabled due to CIDR overlap. |
| By default (API server mode), creating an IPPool with a CIDR that overlaps an existing pool is rejected synchronously at creation time. | ||
|
|
||
| When using [native v3 CRDs](../../operations/native-v3-crds.mdx), CIDR overlap validation is **asynchronous**. Pools with overlapping CIDRs are created successfully but receive a `Disabled` status condition. IPAM does not allocate addresses from disabled pools. Check the IPPool status to identify any pools that have been disabled due to CIDR overlap. | ||
| When using [native v3 CRDs](../../operations/native-v3-crds.mdx), CIDR overlap validation for pools created with `kubectl` is **asynchronous**. Pools with overlapping CIDRs are created successfully but receive an `Allocatable` status condition set to `False` with reason `CIDROverlap`. IPAM does not allocate addresses from disabled pools. Check the IPPool status to identify any pools that have been disabled due to CIDR overlap. |
| In API server mode, creating an IPPool with a CIDR that overlaps an existing pool is rejected synchronously at creation time. | ||
|
|
||
| When using [native v3 CRDs](../../operations/native-v3-crds.mdx), CIDR overlap validation is **asynchronous**. Pools with overlapping CIDRs are created successfully but receive a `Disabled` status condition. IPAM does not allocate addresses from disabled pools. Check the IPPool status to identify any pools that have been disabled due to CIDR overlap. | ||
| When using [native v3 CRDs](../../operations/native-v3-crds.mdx), CIDR overlap validation for pools created with `kubectl` is **asynchronous**. Pools with overlapping CIDRs are created successfully but receive an `Allocatable` status condition set to `False` with reason `CIDROverlap`. IPAM does not allocate addresses from disabled pools. Check the IPPool status to identify any pools that have been disabled due to CIDR overlap. |
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.
Fixes inaccuracies on the IPPool reference page, found and verified with the calico-fact-check skill.
Changes next, 3.33, 3.32 and 3.31. Each fix was reproduced on a kind cluster running that tree's release: v3.33.0 for next and 3.33, v3.32.2 for 3.32, v3.31.7 for 3.31. The CIDR overlap fixes were reproduced in both API server mode and native v3 CRD mode.
Not changed, for follow-up:
Previous attempt: #3079.