erip-7db5dfdcf7-jkjpw 1/1 Running 0 66s pod-to-b-multi-node-headless-7d44b85d69-mtscc 1/1 Running 0 66s pod-to-b-multi-node-nodeport-7ffc76db7c-rrw82 started, use port forwarding for the hubble-ui service. This allows opening the UI locally on a browser: kubectl port-forward -n $CILIUM_NAMESPACE svc/hubble-ui --address 0.0.0.0 --address :: 12000:80 erip-7db5dfdcf7-jkjpw 1/1 Running 0 66s pod-to-b-multi-node-headless-7d44b85d69-mtscc 1/1 Running 0 66s pod-to-b-multi-node-nodeport-7ffc76db7c-rrw82

erip-7db5dfdcf7-jkjpw 1/1 Running 0 66s pod-to-b-multi-node-headless-7d44b85d69-mtscc 1/1 Running 0 66s pod-to-b-multi-node-nodeport-7ffc76db7c-rrw82 erip-7db5dfdcf7-jkjpw 1/1 Running 0 66s pod-to-b-multi-node-headless-7d44b85d69-mtscc 1/1 Running 0 66s pod-to-b-multi-node-nodeport-7ffc76db7c-rrw82 erip-7db5dfdcf7-jkjpw 1/1 Running 0 66s pod-to-b-multi-node-headless-7d44b85d69-mtscc 1/1 Running 0 66s pod-to-b-multi-node-nodeport-7ffc76db7c-rrw82

erip-7db5dfdcf7-jkjpw 1/1 Running 0 66s pod-to-b-multi-node-headless-7d44b85d69-mtscc 1/1 Running 0 66s pod-to-b-multi-node-nodeport-7ffc76db7c-rrw82 rip-7db5dfdcf7-jkjpw 1/1 Running 0 66s pod-to-b-multi-node-headless-7d44b85d69-mtscc 1/1 Running 0 66s pod-to-b-multi-node-nodeport-7ffc76db7c-rrw82 erip-7db5dfdcf7-jkjpw 1/1 Running 0 66s pod-to-b-multi-node-headless-7d44b85d69-mtscc 1/1 Running 0 66s pod-to-b-multi-node-nodeport-7ffc76db7c-rrw82

nh4v 1/1 Running 0 68s host-to-b-multi-node-clusterip-585db65b4d-x74nz 1/1 Running 0 68s host-to-b-multi-node-headless-77c64bc7d8-kgf8p nh4v 1/1 Running 0 68s host-to-b-multi-node-clusterip-585db65b4d-x74nz 1/1 Running 0 68s host-to-b-multi-node-headless-77c64bc7d8-kgf8p nh4v 1/1 Running 0 68s host-to-b-multi-node-clusterip-585db65b4d-x74nz 1/1 Running 0 68s host-to-b-multi-node-headless-77c64bc7d8-kgf8p

from empire-backup. The full policy can be reviewed by opening the URL in the command below in a browser. Apply this Kafka-aware network security policy using kubectl in the main window: $ kubectl create c593fc30-bf57-11e8-98e6- f1a9f45fc4d8 | 5e22159b-f3a9-4f8a-9944-97375df570e9 | True 3c0ae2d1-c836-4aa4-8fe2-5db6cc1f92fc | c7af1400-bf57-11e8-98e6- f1a9f45fc4d8 | 0ccb3df7-78d0-4434-8a7f-4bfa8d714275 | True 11211/TCP 14m NAME READY STATUS RESTARTS AGE pod/a-wing-67db8d5fcc-dpwl4 1/1 Running 0 14m pod/alliance-tracker-6b6447bd69-sz5hz 1/1

from empire-backup. The full policy can be reviewed by opening the URL in the command below in a browser. Apply this Kafka-aware network security policy using kubectl in the main window: $ kubectl create c593fc30-bf57-11e8-98e6- f1a9f45fc4d8 | 5e22159b-f3a9-4f8a-9944-97375df570e9 | True 3c0ae2d1-c836-4aa4-8fe2-5db6cc1f92fc | c7af1400-bf57-11e8-98e6- f1a9f45fc4d8 | 0ccb3df7-78d0-4434-8a7f-4bfa8d714275 | True 11211/TCP 14m NAME READY STATUS RESTARTS AGE pod/a-wing-67db8d5fcc-dpwl4 1/1 Running 0 14m pod/alliance-tracker-6b6447bd69-sz5hz

from empire-backup. The full policy can be reviewed by opening the URL in the command below in a browser. Apply this Ka�a-aware network security policy using kubectl in the main window: $ kubectl create eabf5185-376b-4d4a-a5b5-99f912d98279 | c593fc30-bf57-11e8-98e6-f1a9f45fc4d 3c0ae2d1-c836-4aa4-8fe2-5db6cc1f92fc | c7af1400-bf57-11e8-98e6-f1a9f45fc4d 31a292e0-2e28-4a7d-8c84-8d4cf0c57483 | c4e0d8d0-bf 11211/TC NAME READY STATUS RESTARTS AGE pod/a-wing-67db8d5fcc-dpwl4 1/1 Running 0 14m pod/alliance-tracker-6b6447bd69-sz5hz 1/1