Update dest and src endpoint networkset type descriptions for clarity#2509
Open
dimitri-nicolo wants to merge 2 commits intotigera:mainfrom
Open
Update dest and src endpoint networkset type descriptions for clarity#2509dimitri-nicolo wants to merge 2 commits intotigera:mainfrom
dimitri-nicolo wants to merge 2 commits 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. |
Contributor
There was a problem hiding this comment.
Pull request overview
This PR clarifies the documentation for how Calico determines src_type/source_type and dest_type/dest_type endpoint classifications in Elastic L7 and flow logs, especially when multiple NetworkSets match. The updates make the selection order and CIDR-vs-domain precedence explicit across Calico Enterprise and Calico Cloud, including specific versioned docs.
Changes:
- Update L7 datatypes docs for Calico Enterprise (current and versioned 3.22-2, 3.23-1) and Calico Cloud to describe NetworkSet selection priority: namespace-specific, then GlobalNetworkSets, then other namespaces, with CIDR matches preferred over domain matches.
- Update flow datatypes docs for the same products/versions to use the same, more precise wording for
source_typeanddest_type. - Normalize line-number annotations in the affected tables so the
src_type/source_typeanddest_typerows are properly numbered.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
calico-enterprise_versioned_docs/version-3.23-1/observability/elastic/l7/datatypes.mdx |
Clarifies src_type and dest_type selection order and CIDR-vs-domain precedence in L7 log field docs for Enterprise 3.23-1. |
calico-enterprise_versioned_docs/version-3.23-1/observability/elastic/flow/datatypes.mdx |
Updates dest_type and source_type flow log field docs with explicit NetworkSet selection rules for Enterprise 3.23-1. |
calico-enterprise_versioned_docs/version-3.22-2/observability/elastic/l7/datatypes.mdx |
Aligns Enterprise 3.22-2 L7 src_type/dest_type descriptions with the detailed matching and precedence rules. |
calico-enterprise_versioned_docs/version-3.22-2/observability/elastic/flow/datatypes.mdx |
Aligns Enterprise 3.22-2 flow dest_type/source_type docs with the new, more precise selection description. |
calico-enterprise/observability/elastic/l7/datatypes.mdx |
Updates current Enterprise L7 src_type/dest_type docs to include explicit namespace priority and CIDR-over-domain precedence. |
calico-enterprise/observability/elastic/flow/datatypes.mdx |
Updates current Enterprise flow dest_type/source_type docs with the same clarified NetworkSet selection rules. |
calico-cloud/observability/elastic/l7/datatypes.mdx |
Updates Calico Cloud L7 src_type/dest_type docs to match the clarified NetworkSet matching behavior. |
calico-cloud/observability/elastic/flow/datatypes.mdx |
Updates Calico Cloud flow dest_type/source_type docs with the clarified selection priority and CIDR-vs-domain rules. |
dimitri-nicolo
force-pushed
the
dimitri-EV-6372
branch
2 times, most recently
from
909f785 to
380a1dd
Compare
dimitri-nicolo
changed the title
…nd L7 log data types
dimitri-nicolo
force-pushed
the
dimitri-EV-6372
branch
from
380a1dd to
c0f150c
Compare
ctauchen
reviewed
Feb 4, 2026
Collaborator
ctauchen
left a comment
ctauchen
left a comment
There was a problem hiding this comment.
Thanks, @dimitri-nicolo. LGTM. Merge?
pasanw
approved these changes
Feb 4, 2026
Contributor
Author
@ctauchen Thanks for the quick review. Yes, please merge |
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
3 participants
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.
Product Version(s):
Calico Enterprise (Next, 3.23-1), Calico Cloud
Issue:
[EV-6372](https://tigera.atlassian.net/browse/EV-6372) Clarify NetworkSet selection priority and tie-breaking logic in Flow and L7 log data types.
Link to docs preview:
SME review:
DOCS review:
Additional information:
Merge checklist: