-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS-11625:Viewing Network events in Network Observability #85999
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.
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
17 changes: 17 additions & 0 deletions
17
modules/network-observability-networking-events-overview.adoc
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
// Module included in the following assemblies: | ||
// | ||
// network_observability/observing-network-traffic.adoc | ||
|
||
:_mod-docs-content-type: CONCEPT | ||
[id="network-observability-networking-events-overview_{context}"] | ||
= OVN Kubernetes networking events | ||
:FeatureName: Viewing `NetworkEvents` | ||
include::snippets/technology-preview.adoc[] | ||
|
||
You use network event tracking in Network Observability to gain insight into OVN-Kubernetes events, including network policies, admin network policies, and egress firewalls. You can use the insights from tracking network events to help with the following tasks: | ||
|
||
* Network monitoring: Monitor allowed and blocked traffic, detecting whether packets are allowed or blocked based on network policies and admin network policies. | ||
|
||
* Network security: You can track outbound traffic and see whether it adheres to egress firewall rules. Detect unauthorized outbound connections and flag outbound traffic that violates egress rules. | ||
|
||
See the _Additional resources_ in this section for more information about enabling and working with this view. |
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
Original file line number | Diff line number | Diff line change | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
@@ -0,0 +1,60 @@ | ||||||||||||||||||
// Module included in the following assemblies: | ||||||||||||||||||
// | ||||||||||||||||||
// * network_observability/observing-network-traffic.adoc | ||||||||||||||||||
|
||||||||||||||||||
:_mod-docs-content-type: PROCEDURE | ||||||||||||||||||
[id="network-observability-viewing-network-events_{context}"] | ||||||||||||||||||
= Viewing network events | ||||||||||||||||||
:FeatureName: Viewing `NetworkEvents` | ||||||||||||||||||
include::snippets/technology-preview.adoc[] | ||||||||||||||||||
|
||||||||||||||||||
You can edit the `FlowCollector` to view information about network traffic events, such as network flows that are dropped or allowed by the following resources: | ||||||||||||||||||
|
||||||||||||||||||
* `NetworkPolicy` | ||||||||||||||||||
* `AdminNetworkPolicy` | ||||||||||||||||||
* `BaselineNetworkPolicy` | ||||||||||||||||||
* `EgressFirewall` | ||||||||||||||||||
* `UserDefinedNetwork` isolation | ||||||||||||||||||
* Multicast ACLs | ||||||||||||||||||
|
||||||||||||||||||
.Prerequisites | ||||||||||||||||||
* You must have `OVNObservability` enabled by setting the `TechPreviewNoUpgrade` feature set in the `FeatureGate` custom resource (CR) named `cluster`. For more information, see "Enabling feature sets using the CLI" and "Checking OVN-Kubernetes network traffic with OVS sampling using the CLI". | ||||||||||||||||||
* You have created at least one of the following network APIs: `NetworkPolicy`, `AdminNetworkPolicy`, `BaselineNetworkPolicy`, `UserDefinedNetwork` isolation, multicast, or `EgressFirewall`. | ||||||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I see your point, but I think I'll leave these since I bulleted them in the introduction. |
||||||||||||||||||
|
||||||||||||||||||
.Procedure | ||||||||||||||||||
. In the web console, navigate to *Operators* -> *Installed Operators*. | ||||||||||||||||||
. In the *Provided APIs* heading for the *NetObserv Operator*, select *Flow Collector*. | ||||||||||||||||||
. Select *cluster*, and then select the *YAML* tab. | ||||||||||||||||||
. Configure the `FlowCollector` CR to enable viewing `NetworkEvents`, for example: | ||||||||||||||||||
+ | ||||||||||||||||||
[id="network-observability-flowcollector-configuring-networkevents{context}"] | ||||||||||||||||||
.Example `FlowCollector` configuration | ||||||||||||||||||
[source, yaml] | ||||||||||||||||||
---- | ||||||||||||||||||
apiVersion: flows.netobserv.io/v1beta2 | ||||||||||||||||||
kind: FlowCollector | ||||||||||||||||||
metadata: | ||||||||||||||||||
name: cluster | ||||||||||||||||||
spec: | ||||||||||||||||||
agent: | ||||||||||||||||||
type: eBPF | ||||||||||||||||||
ebpf: | ||||||||||||||||||
# sampling: 1 <1> | ||||||||||||||||||
privileged: true <2> | ||||||||||||||||||
features: | ||||||||||||||||||
- "NetworkEvents" | ||||||||||||||||||
---- | ||||||||||||||||||
<1> Optional: The `sampling` parameter is set to a value of 1 so that all network events are captured. If sampling `1` is too resource heavy, set sampling to something more appropriate for your needs. | ||||||||||||||||||
<2> The `privileged` parameter is set to `true` because the `OVN observability` library needs to access local Open vSwitch (OVS) socket and OpenShift Virtual Network (OVN) databases. | ||||||||||||||||||
|
||||||||||||||||||
.Verification | ||||||||||||||||||
. Navigate to the *Network Traffic* view and select the *Traffic flows* table. | ||||||||||||||||||
. You should see the new column, *Network Events*, where you can view information about impacts of one of the following network APIs you have enabled: `NetworkPolicy`, `AdminNetworkPolicy`, `BaselineNetworkPolicy`, `UserDefinedNetwork` isolation, multicast, or egress firewalls. | ||||||||||||||||||
|
||||||||||||||||||
An example of the kind of events you could see in this column is as follows: | ||||||||||||||||||
+ | ||||||||||||||||||
.Example of Network Events output | ||||||||||||||||||
[source,text] | ||||||||||||||||||
---- | ||||||||||||||||||
<Dropped_or_Allowed> by <network_event_and_event_name>, direction <Ingress_or_Egress> | ||||||||||||||||||
---- |
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
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.
Uh oh!
There was an error while loading. Please reload this page.