DESIRED CAPACITY INSTANCE TYPE IMAGE ID test-cluster ng-25560078 2019-07-23T06:05:35Z 0 2 0 m5.large ami- 0923e4b35a30a5f53 DESIRED CAPACITY INSTANCE TYPE IMAGE ID test-cluster ng-25560078 2019-07-23T06:05:35Z 0 2 0 m5.large ami- 0923e4b35a30a5f53 1.0/bin/kafka-console-producer.sh --broker- list=kafka:9092 --topic=authaudit test message [2017-12-07 02:13:47,020] ERROR Error when sending message to topic authaudit with key: null, value: 12 bytes

DESIRED CAPACITY INSTANCE TYPE IMAGE ID test-cluster ng-25560078 2019-07-23T06:05:35Z 0 2 0 m5.large ami- 0923e4b35a30a5f53 DESIRED CAPACITY INSTANCE TYPE IMAGE ID test-cluster ng-25560078 2019-07-23T06:05:35Z 0 2 0 m5.large ami- 0923e4b35a30a5f53 1.0/bin/kafka-console-producer.sh --broker- list=kafka:9092 --topic=authaudit test message [2017-12-07 02:13:47,020] ERROR Error when sending message to topic authaudit with key: null, value: 12 bytes

$ kubectl exec ${POD_LOGGER_V1} -c authaudit-logger -ti -- /opt/kafka_2.11 test message [2017-12-07 02:13:47,020] ERROR Error when sending message to topic authaud org.apache.kafka.common.errors.To ${POD_LOGGER_V1} -c authaudit-logger -ti -- /opt/kafka_2.11 [2017-12-07 03:08:54,513] WARN Not authorized to read from topic credit-ca [2017-12-07 03:08:54,517] ERROR Error processing message, terminating cons client or server: “tcpdump -s 0 port 3306 -w mysql.pcap”. More Info [h�ps://linuxexplore.com/2012/06/07/use-tcpdump-to-capture-in-a-pcap- file-wireshark-dump/] In our example r2d2 protocol, we’ll keep the

the CIDRs, you will need to make sure that Helm values in ${CLUSTER_NAME}/manifests/cluster-network-07-cilium-ciliumconfig.yaml reflect those changes. Namely clusterNetwork should match nativeRoutingCIDR -cilium-* You can set any custom Helm values by editing ${CLUSTER_NAME}/manifests/cluster-network-07-cilium-ciliumconfig.yaml. It is also possible to update Helm values once the cluster is running by 1.0/bin/kafka-console-producer.sh --broker- list=kafka:9092 --topic=authaudit test message [2017-12-07 02:13:47,020] ERROR Error when sending message to topic authaudit with key: null, value: 12 bytes

1.0/bin/kafka-console-producer.sh --broker- list=kafka:9092 --topic=authaudit test message [2017-12-07 02:13:47,020] ERROR Error when sending message to topic authaudit with key: null, value: 12 bytes --topic=credit-card-payments [2017-12-07 03:08:54,513] WARN Not authorized to read from topic credit-card-payments. (org.apache.kafka.clients.consumer.internals.Fetcher) [2017-12-07 03:08:54,517] ERROR Error processing client or server: “tcpdump -s 0 port 3306 -w mysql.pcap”. More Info [https://linuxexplore.com/2012/06/07/use-tcpdump-to-capture-in-a-pcap-file-wireshark-dump/] In our example r2d2 protocol, we’ll keep the

1.0/bin/kafka-console-producer.sh --broker- list=kafka:9092 --topic=authaudit test message [2017-12-07 02:13:47,020] ERROR Error when sending message to topic authaudit with key: null, value: 12 bytes --topic=credit-card-payments [2017-12-07 03:08:54,513] WARN Not authorized to read from topic credit-card-payments. (org.apache.kafka.clients.consumer.internals.Fetcher) [2017-12-07 03:08:54,517] ERROR Error processing client or server: “tcpdump -s 0 port 3306 -w mysql.pcap”. More Info [https://linuxexplore.com/2012/06/07/use-tcpdump-to-capture-in-a-pcap-file-wireshark-dump/] In our example r2d2 protocol, we’ll keep the

the CIDRs, you will need to make sure that Helm values in ${CLUSTER_NAME}/manifests/cluster-network-07-cilium-ciliumconfig.yaml reflect those changes. Namely clusterNetwork should match ipv4NativeRoutingCIDR -cilium-* You can set any custom Helm values by editing ${CLUSTER_NAME}/manifests/cluster-network-07-cilium-ciliumconfig.yaml. It is also possible to update Helm values once the cluster is running by 1.0/bin/kafka-console-producer.sh --broker- list=kafka:9092 --topic=authaudit test message [2017-12-07 02:13:47,020] ERROR Error when sending message to topic authaudit with key: null, value: 12 bytes