keep the setup small, we will just launch a small number of pods to represent this setup: kafka-broker : A single pod running Kafka and Zookeeper representing the Kafka cluster (label app=kafka). empire-hq empire-announce topic (label app=empire-outpost). All pods other than kafka-broker are Kafka clients, which need access to the kafka- broker container on TCP port 9092 in order to send Kafka protocol messages Zookeeper. $ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.6/ex deployment "kafka-broker" created deployment "zookeeper" created service "zook" created service "kafka-service" created deployment

To keep the setup small, we will just launch a small number of pods to represent this setup: ka�a-broker : A single pod running Ka�a and Zookeeper represen�ng the Ka�a cluster (label app=ka�a). empire-hq empire-announce topic (label app=empire-outpost). All pods other than ka�a-broker are Ka�a clients, which need access to the ka�a-broker container on TCP port 9092 in order to send Ka�a protocol messages. The Zookeeper. $ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/ex deployment "kafka-broker" created deployment "zookeeper" created service "zook" created service "kafka-service" created deployment

keep the setup small, we will just launch a small number of pods to represent this setup: kafka-broker : A single pod running Kafka and Zookeeper representing the Kafka cluster (label app=kafka). empire-hq empire-announce topic (label app=empire-outpost). All pods other than kafka-broker are Kafka clients, which need access to the kafka- broker container on TCP port 9092 in order to send Kafka protocol messages Zookeeper. $ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.7/ex deployment "kafka-broker" created deployment "zookeeper" created service "zook" created service "kafka-service" created deployment

required for your cluster. After a few minutes, you will see that the Nodes overview will show an error message in the Rancher UI: This error is expected. The Kubernetes components are not able to fully communicate keep the setup small, we will just launch a small number of pods to represent this setup: kafka-broker : A single pod running Kafka and Zookeeper representing the Kafka cluster (label app=kafka). empire-hq empire-announce topic (label app=empire-outpost). All pods other than kafka-broker are Kafka clients, which need access to the kafka- broker container on TCP port 9092 in order to send Kafka protocol messages

required for your cluster. After a few minutes, you will see that the Nodes overview will show an error message in the Rancher UI: This error is expected. The Kubernetes components are not able to fully communicate Hubble server address (default: localhost:4245). For more information, check out Hubble CLI’s help message by running hubble help status or hubble help observe as well as hubble config for configuring Hubble keep the setup small, we will just launch a small number of pods to represent this setup: kafka-broker : A single pod running Kafka and Zookeeper representing the Kafka cluster (label app=kafka). empire-hq

required for your cluster. After a few minutes, you will see that the Nodes overview will show an error message in the Rancher UI: This error is expected. The Kubernetes components are not able to fully communicate keep the setup small, we will just launch a small number of pods to represent this setup: kafka-broker : A single pod running Kafka and Zookeeper representing the Kafka cluster (label app=kafka). empire-hq empire-announce topic (label app=empire-outpost). All pods other than kafka-broker are Kafka clients, which need access to the kafka- broker container on TCP port 9092 in order to send Kafka protocol messages

required for your cluster. After a few minutes, you will see that the Nodes overview will show an error message in the Rancher UI: This error is expected. The Kubernetes components are not able to fully communicate Hubble server address (default: localhost:4245). For more information, check out Hubble CLI’s help message by running hubble help status or hubble help observe as well as hubble config for configuring Hubble keep the setup small, we will just launch a small number of pods to represent this setup: kafka-broker : A single pod running Kafka and Zookeeper representing the Kafka cluster (label app=kafka). empire-hq