@@ -54,7 +54,7 @@ The `CiliumNodeConfig` resource defines encryption settings for Cilium. It enabl
5454 kubectl apply -f cilium-encryption.yaml
5555 ```
5656
57- ## Restarting the Cilium DaemonSet**
57+ ## Restarting the Cilium DaemonSet
5858
5959After creating the ` CiliumNodeConfig ` , you must restart Cilium to apply these encryption settings.
6060
@@ -74,7 +74,7 @@ After creating the `CiliumNodeConfig`, you must restart Cilium to apply these en
7474 ```
7575 All Cilium pods should eventually show as ** Running** and ** Ready** .
7676
77- ## Validating Encryption
77+ ## Validating encryption
7878
7979In this step, you will deploy test applications along with a ` tcpdump ` DaemonSet to observe network traffic before and after enabling encryption.
8080
@@ -86,7 +86,7 @@ Below is an example YAML manifest that deploys:
8686* A ** curl** Deployment that continuously makes requests to ** nginx** .
8787* A ** tcpdump** DaemonSet to capture traffic on each node’s ` kapsule0 ` interface.
8888
89- 1 . Save the following as ` test-and-tcpdump.yaml ` :
89+ 1 . Save the following template in a ` test-and-tcpdump.yaml ` file :
9090 ```
9191 apiVersion: apps/v1
9292 kind: Deployment
@@ -230,7 +230,7 @@ kubectl logs -n default daemonset/tcpdump -f
230230
231231(Select any pod if multiple logs are shown.)
232232
233- ### Checking encryption status in Cilium**
233+ ### Checking encryption status in Cilium
234234
235235After applying the ` CiliumNodeConfig ` and restarting Cilium, you can verify the configuration by checking each Cilium pod:
236236
0 commit comments