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

Management:/:/sbin/nologin systemd-resolve:x:193:193:systemd Resolver:/:/sbin/nologin dbus:x:81:81:System message bus:/:/sbin/nologin sshd:x:74:74:Privilege-separated SSH:/var/empty/sshd:/sbin/nologin chrony:x process in my computer is 26752, we can use that id to kill it. $ kill 26752 If there is no error message, you’ll find that Firefox has disappeared. Finding out list of open files lsof command will show dev-mqueue.mount loaded active mounted POSIX Message Queue File System home.mount loaded active

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

Management:/:/sbin/nologin systemd-resolve:x:193:193:systemd Resolver:/:/sbin/nologin dbus:x:81:81:System message bus:/:/sbin/nologin sshd:x:74:74:Privilege-separated SSH:/var/empty/sshd:/sbin/nologin chrony:x: process in my computer is 26752, we can use that id to kill it. $ kill 26752 If there is no error message, you’ll find that Firefox has disappeared. 7.4 Finding out list of open files lsof command will loaded active ˓→mounted Huge Pages File System dev-mqueue.mount loaded active ˓→mounted POSIX Message Queue File System home.mount loaded active ˓→mounted /home proc-fs-nfsd.mount loaded active ˓→mounted

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

service repository Platform service management Edge- installer Edge- Logger Middleware MQTT Broker SQLlite Edge- Monitor Device Mapper Device Lib Device Adapter Device Driver openEuler 21.09 You can share your opinions or suggestions in the SIG by submitting an issue, which is a public message that is open to everyone. To attract more attention, you can also attach the issue link to the email