Skip to content

[enterprise-4.21] [OCPBUGS#77520]: Add note about EndpointSlice limitations to commatrix plugin docs #115813

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

Merged
gaurav-nelson merged 1 commit into from
Jul 21, 2026
+6 −1
Merged

[enterprise-4.21] [OCPBUGS#77520]: Add note about EndpointSlice limitations to commatrix plugin docs #115813

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
3 changes: 2 additions & 1 deletion modules/network-commatrix-plugin-install.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,8 @@ You can install the `commatrix` plugin from the Red Hat Ecosystem Catalog.

[NOTE]
====
You can also install the `commatrix` plugin by using Krew. For more information, see "{cli-manager} overview".
* You can also install the `commatrix` plugin by using Krew. For more information, see "{cli-manager} overview".
* The communication matrix does not include ports from non-core Operators or other software that do not expose a `Service` object. For a complete view of listening ports, run the `generate` command with the `--host-open-ports` flag.
====

.Prerequisites
Expand Down
4 changes: 4 additions & 0 deletions modules/network-commatrix-plugin-intro.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,3 +16,7 @@ The plugin generates ingress flows to {product-title} services for the following
* {sno-caps} on {aws-short}

The plugin outputs the network flow data in various formats, such as CSV or JSON.

The communication matrix uses `EndpointSlice` objects to discover exposed ports. Kubernetes automatically creates `EndpointSlice` objects for each `Service` object. Starting with {product-title} {product-version}, the matrix fully covers all core {product-title} ports. However, non-core Operators or other software that expose ports without a corresponding `Service` object do not appear in the matrix, such as host-level services, monitoring agents, or third-party software.

To discover all listening ports on cluster nodes, use the `--host-open-ports` flag. This flag captures ports that are open on the hosts but are not defined through `Service` or `EndpointSlice` objects. You can compare this output with the declared ports by using the diff file generated by the plugin, which shows the differences between the intended and actual state.