$CILIUM_NAMESPACE svc/hubble-relay --address 0.0.0.0 --address :: 4245:80 In a separate terminal window, run the hubble status command specifying the Hubble Relay address: $ hubble --server localhost:4245 $CILIUM_NAMESPACE svc/hubble-relay --address 0.0.0.0 --address :: 4245:80 In a separate terminal window, run the hubble status command specifying the Hubble Relay address: $ hubble --server localhost:4245 $CILIUM_NAMESPACE svc/hubble-relay --address 0.0.0.0 --address :: 4245:80 In a separate terminal window, run the hubble status command specifying the Hubble Relay address: $ hubble --server localhost:4245

we recommend opening them in the pa�ern shown in the image below, but this is op�onal. In each window, use copy-paste to have each terminal provide a shell inside each pod. empire-hq terminal: $ HQ_POD=$(kubectl Ka�a topic: In the empire-backup window, start listening on the top-secret deathstar-plans topic: $ ./kafka-consume.sh --topic deathstar-plans In the outpost-8888 window, start listening to empire-announcement: empire-announcement: $ ./kafka-consume.sh --topic empire-announce Do the same in the outpost-9999 window: $ ./kafka-consume.sh --topic empire-announce Now from the empire-hq, first produce a message to the empire-announce

we recommend opening them in the pattern shown in the image below, but this is optional. In each window, use copy-paste to have each terminal provide a shell inside each pod. empire-hq terminal: $ HQ_POD=$(kubectl Kafka topic: In the empire-backup window, start listening on the top-secret deathstar-plans topic: $ ./kafka-consume.sh --topic deathstar-plans In the outpost-8888 window, start listening to empire-announcement: empire-announcement: $ ./kafka-consume.sh --topic empire-announce Do the same in the outpost-9999 window: $ ./kafka-consume.sh --topic empire-announce Now from the empire-hq, first produce a message to the empire-announce

meaning that cilium monitor will report each HTTP request and response. To see this, open a new window and run the following command to identity the name of the cilium pod (e.g, cilium-97s78) that is Cilium: kubectl exec -it -n kube-system cilium-d5x8v -- cilium monitor -t l7 Next in the original window, from the mediabot pod we can access artii.herokuapp.com via HTTPS: $ kubectl exec -it mediabot 'https://artii.herokuapp.com/make?text=cilium&font=univers' ... ... Looking back at the cilium monitor window, you will see each individual HTTP request and response. For example: -> Request http from 2585

click the box to Edit as YAML. The configuration for the cluster will open up in an editor in the window. Remove all configuration pertaining to the default network plugin: Ensure that network plugin yet. In the Rancher UI, navigate to Tools -> Catalogs and click the Add Catalog button: In the window that opens, add the official Cilium Helm v3 chart repository to the Rancher catalog: Once added meaning that cilium monitor will report each HTTP request and response. To see this, open a new window and run the following command to identity the name of the cilium pod (e.g, cilium-97s78) that is

click the box to Edit as YAML. The configuration for the cluster will open up in an editor in the window. Remove all configuration pertaining to the default network plugin: Ensure that network plugin yet. In the Rancher UI, navigate to Tools -> Catalogs and click the Add Catalog button: In the window that opens, add the official Cilium Helm v3 chart repository to the Rancher catalog: Once added meaning that cilium monitor will report each HTTP request and response. To see this, open a new window and run the following command to identity the name of the cilium pod (e.g, cilium-97s78) that is

click the box to Edit as YAML. The configuration for the cluster will open up in an editor in the window. Remove all configuration pertaining to the default network plugin: Ensure that network plugin yet. In the Rancher UI, navigate to Tools -> Catalogs and click the Add Catalog button: In the window that opens, add the official Cilium Helm v3 chart repository to the Rancher catalog: Once added meaning that cilium monitor will report each HTTP request and response. To see this, open a new window and run the following command to identity the name of the cilium pod (e.g, cilium-97s78) that is