brokers 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 empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized while fetching metadata with correlation id 2 : {deathstar-plans=TOPIC_AUTHORIZATION_FAILED} (org.apache.kafka.clients.NetworkClient) This is blocked as well, thanks to the Cilium network policy. Imagine

Ka�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 --topic empire-a >>[2018-04-10 23:50:34,638] ERROR Error when sending message to topic empi org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized This is because the policy does Star from the Rebel Alliance, this Cassandra demo is Star Wars-themed as well. Apache Cassanadra [h�p://cassandra.apache.org] is a popular NOSQL database focused on delivering high-performance transac�ons

brokers 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 empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized while fetching metadata with correlation id 2 : {deathstar-plans=TOPIC_AUTHORIZATION_FAILED} (org.apache.kafka.clients.NetworkClient) This is blocked as well, thanks to the Cilium network policy. Imagine

brokers 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 empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized while fetching metadata with correlation id 2 : {deathstar-plans=TOPIC_AUTHORIZATION_FAILED} (org.apache.kafka.clients.NetworkClient) This is blocked as well, thanks to the Cilium network policy. Imagine

brokers 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 empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized while fetching metadata with correlation id 2 : {deathstar-plans=TOPIC_AUTHORIZATION_FAILED} (org.apache.kafka.clients.NetworkClient) This is blocked as well, thanks to the Cilium network policy. Imagine

brokers 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 empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized while fetching metadata with correlation id 2 : {deathstar-plans=TOPIC_AUTHORIZATION_FAILED} (org.apache.kafka.clients.NetworkClient) This is blocked as well, thanks to the Cilium network policy. Imagine

brokers 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 empire-announce with key: null, value: 27 bytes with error: (org.apache.kafka.clients.producer.internals.ErrorLoggingCallback) org.apache.kafka.common.errors.TopicAuthorizationException: Not authorized while fetching metadata with correlation id 2 : {deathstar-plans=TOPIC_AUTHORIZATION_FAILED} (org.apache.kafka.clients.NetworkClient) This is blocked as well, thanks to the Cilium network policy. Imagine