Skip to content

Commit 9bd1e13

Browse files
authored
fix issues in what's new 1.8 (#18)
1 parent 248304b commit 9bd1e13

File tree

8 files changed

+12
-13
lines changed

8 files changed

+12
-13
lines changed

content/posts/2025-02-26-whats_new_1_8/index.md renamed to content/posts/2025-02-26-whats-new-1-8/index.md

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,6 @@ title: "What's new in Network Observability 1.8"
44
description: "New features: Packet Translation, eBPF resource reduction, Network Events, eBPF flow filter enhancements, UDN Observability, eBPF Manager support"
55
tags: network,observability,new,xlate,OVN,UDN,eBPF
66
authors: [stleerh]
7-
rhDevBlogURL:
87
---
98

109
_Thanks to Joel Takvorian, Mohamed S. Mahmoud, Julien Pinsonneau, Mike Fiedler, Sara Thomas, and Mehul Modi for reviewing._
@@ -37,7 +36,7 @@ Figure 2: Flows table with Packet Translation
3736

3837
To enable this feature in FlowCollector, enter `oc edit flowcollector` and configure the following in the **ebpf** section:
3938

40-
```
39+
```yaml
4140
spec:
4241
agent:
4342
ebpf:
@@ -50,7 +49,7 @@ spec:
5049
5150
To create a basic Nginx web server, enter the following commands on the command line. I created two of them, one with the namespace "chiefs" and another with namespace "eagles".
5251
53-
```
52+
```bash
5453
oc new-project chiefs
5554
oc adm policy add-scc-to-group anyuid system:authenticated
5655
oc create deployment nginx --image=nginx
@@ -90,7 +89,7 @@ With OVN-Kubernetes and Network Events, you can see what's happening with a pack
9089

9190
On OVN-Kubernetes, this is disabled by default since this is a Technology Preview feature, so enable it by adding the feature gate named **OVNObservability**. On the command line, enter `oc edit featuregate` and change the **spec** section to:
9291

93-
```
92+
```yaml
9493
spec:
9594
featureSet: CustomNoUpgrade
9695
customNoUpgrade:
@@ -104,7 +103,7 @@ This can take upwards of *10+ minutes* for this to take effect, so be patient.
104103
105104
To enable this feature in FlowCollector, enter `oc edit flowcollector` and configure the following in the **ebpf** section:
106105

107-
```
106+
```yaml
108107
spec:
109108
agent:
110109
ebpf:
@@ -154,7 +153,7 @@ In summary, use `cidr` for the client side address and `peerCIDR` for the server
154153

155154
Each rule can have its own sampling rate. For example, you might want the eBPF Agent to sample all external traffic on source and destination, but for internal traffic, it's sufficient to sample at 50. Listing 5 shows how this can be done, assuming the default IP settings of 10.128.0.0/14 for pods and 172.30.0.0/16 for services.
156155

157-
```
156+
```yaml
158157
spec:
159158
agent:
160159
type: eBPF
@@ -183,7 +182,7 @@ The last rule with CIDR 0.0.0.0/0 is necessary to explicitly tell it to process
183182

184183
Another new option is **pktDrops**. With **pktDrops: true** and **action: Accept**, it includes the packet only if it's dropped. The prerequisite is that the eBPF feature, **PacketDrop** is enabled, which requires eBFP to be in **privileged** mode. Note this currently is not supported if you enable the **NetworkEvent** feature. Listing 6 shows an example configuration.
185184

186-
```
185+
```yaml
187186
spec:
188187
agent:
189188
type: eBPF
@@ -211,7 +210,7 @@ Kubernetes networking consists of a flat Layer 3 network and a single IP address
211210

212211
To enable this feature in FlowCollector, enter `oc edit flowcollector` and configure the following in the **ebpf** section:
213212

214-
```
213+
```yaml
215214
spec:
216215
agent:
217216
ebpf:
@@ -225,7 +224,7 @@ spec:
225224

226225
Let's create a user-defined network based on a namespace (Listing 8).
227226

228-
```
227+
```yaml
229228
apiVersion: v1
230229
kind: Namespace
231230
metadata:
@@ -242,7 +241,7 @@ You can use `oc apply` with the content in Listing 8, or copy and paste this int
242241

243242
Now create a UserDefinedNetwork instance (Listing 9). Again, use `oc apply` or paste into OpenShift web console.
244243

245-
```
244+
```yaml
246245
apiVersion: k8s.ovn.org/v1
247246
kind: UserDefinedNetwork
248247
metadata:
@@ -260,9 +259,9 @@ spec:
260259

261260
Now if you add a pod into this namespace, it will automatically have a secondary interface that is part of the UDN. You can confirm this by entering the commands in Listing 10.
262261

263-
```
262+
```bash
264263
oc project 49ers
265-
pod=$(oc get --no-headers pods | awk '{print $1;}') # get pod name
264+
pod=$(oc get --no-headers pods | awk '{ print $1;}') # get pod name
266265
oc describe pod/$pod # should see two interfaces mentioned in Annotations
267266
```
268267

@@ -289,7 +288,7 @@ First, install the eBPF Manager Operator from **Operators > OperatorHub**. This
289288

290289
Then install Network Observability and configure the FlowCollector resource in Listing 11. Because this is a Developer Preview feature, delete the FlowCollector instance if you already have one and create a new instance, rather than edit an existing one.
291290

292-
```
291+
```yaml
293292
spec:
294293
agent:
295294
ebpf:

0 commit comments

Comments
 (0)