Cilium v1.6 Documentationbrokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle 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 : A pod representing the Empire’s Headquarters Kubernetes Service for both Kafka and Zookeeper. $ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.6/ex deployment "kafka-broker" created deployment "zookeeper" created service "zook" created0 码力 | 734 页 | 11.45 MB | 1 年前3
 Cilium v1.7 Documentationbrokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle 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 : A pod representing the Empire’s Headquarters Kubernetes Service for both Kafka and Zookeeper. $ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.7/ex deployment "kafka-broker" created deployment "zookeeper" created service "zook" created0 码力 | 885 页 | 12.41 MB | 1 年前3
 Cilium v1.5 DocumentationKa�a brokers o�en handles many different topics at once (read this Introduc�on to Ka�a [h�ps://ka�a.apache.org/intro] for more background). In our simple example, the Empire uses a Ka�a cluster to handle 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 : A pod represen�ng the Empire’s Headquarters Kubernetes Service for both Ka�a and Zookeeper. $ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.5/ex deployment "kafka-broker" created deployment "zookeeper" created service "zook" created0 码力 | 740 页 | 12.52 MB | 1 年前3
 Cilium v1.8 Documentationbrokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle 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 : A pod representing the Empire’s Headquarters Kubernetes Service for both Kafka and Zookeeper. $ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.8/ex deployment "kafka-broker" created deployment "zookeeper" created service "zook" created0 码力 | 1124 页 | 21.33 MB | 1 年前3
 Cilium v1.9 Documentationbrokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle 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 : A pod representing the Empire’s Headquarters Kubernetes Service for both Kafka and Zookeeper. $ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.9/ex deployment "kafka-broker" created deployment "zookeeper" created service "zook" created0 码力 | 1263 页 | 18.62 MB | 1 年前3
 Cilium v1.10 Documentationbrokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle 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 : A pod representing the Empire’s Headquarters Kubernetes Service for both Kafka and Zookeeper. $ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.10/e deployment "kafka-broker" created deployment "zookeeper" created service "zook" created0 码力 | 1307 页 | 19.26 MB | 1 年前3
 Cilium v1.11 Documentationbrokers often handles many different topics at once (read this Introduction to Kafka [https://kafka.apache.org/intro] for more background). In our simple example, the Empire uses a Kafka cluster to handle 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 : A pod representing the Empire’s Headquarters Kubernetes Service for both Kafka and Zookeeper. $ kubectl create -f https://raw.githubusercontent.com/cilium/cilium/v1.11/e deployment "kafka-broker" created deployment "zookeeper" created service "zook" created0 码力 | 1373 页 | 19.37 MB | 1 年前3
共 7 条
- 1
 













