deathstar.default.svc.cluster.local/v1/request-landing This request will hang, so press Control-C to kill the curl request, or wait for it to time out. Inspecting the Policy If we run cilium endpoint list consumer to a producer, sending “malicious” data to all other consumers on the topic. To prove this, kill the existing kafka-consume.sh command in the outpost-9999 window by typing control-C and instead run: deathstar.default.svc.cluster.local/v1/request-landing This request will hang, so press Control-C to kill the curl request, or wait for it to time out. We hope you enjoyed the tutorial. Feel free to play

curl -s -XPOST deathstar.default.svc.cluster.local/ This request will hang, so press Control-C to kill the curl request, or wait for it to �me out. Inspecting the Policy If we run cilium endpoint list consumer to a producer, sending “malicious” data to all other consumers on the topic. To prove this, kill the exis�ng kafka-consume.sh command in the outpost- 9999 window by typing control-C and instead through the /proc/sys/kernel/unprivileged_bpf_disabled sysctl knob. This is on purpose a one-�me kill switch, meaning once set to 1 , there is no op�on to reset it back to 0 un�l a new kernel reboot

hang because the xwing pod does not have the org=empire label required by policy. Press Control-C to kill the curl request, or wait for it to time out. kubectl exec xwing -- curl -s -XPOST deathstar.default deathstar.default.svc.cluster.local/v1/request-landing This request will hang, so press Control-C to kill the curl request, or wait for it to time out. Inspecting the Policy If we run cilium endpoint list consumer to a producer, sending “malicious” data to all other consumers on the topic. To prove this, kill the existing kafka-consume.sh command in the outpost-9999 window by typing control-C and instead run:

deathstar.default.svc.cluster.local/v1/request-landing This request will hang, so press Control-C to kill the curl request, or wait for it to time out. Inspecting the Policy If we run cilium endpoint list consumer to a producer, sending “malicious” data to all other consumers on the topic. To prove this, kill the existing kafka-consume.sh command in the outpost-9999 window by typing control-C and instead run: deathstar.default.svc.cluster.local/v1/request-landing This request will hang, so press Control-C to kill the curl request, or wait for it to time out. We hope you enjoyed the tutorial. Feel free to play

deathstar.default.svc.cluster.local/v1/request-landing This request will hang, so press Control-C to kill the curl request, or wait for it to time out. Inspecting the Policy If we run cilium endpoint list consumer to a producer, sending “malicious” data to all other consumers on the topic. To prove this, kill the existing kafka-consume.sh command in the outpost-9999 window by typing control-C and instead run: through the /proc/sys/kernel/unprivileged_bpf_disabled sysctl knob. This is on purpose a one-time kill switch, meaning once set to 1, there is no option to reset it back to 0 until a new kernel reboot

hang because the xwing pod does not have the org=empire label required by policy. Press Control-C to kill the curl request, or wait for it to time out. kubectl exec xwing -- curl -s -XPOST deathstar.default deathstar.default.svc.cluster.local/v1/request-landing This request will hang, so press Control-C to kill the curl request, or wait for it to time out. Inspecting the Policy If we run cilium endpoint list consumer to a producer, sending “malicious” data to all other consumers on the topic. To prove this, kill the existing kafka-consume.sh command in the outpost-9999 window by typing control-C and instead run:

deathstar.default.svc.cluster.local/v1/request-landing This request will hang, so press Control-C to kill the curl request, or wait for it to time out. Inspecting the Policy If we run cilium endpoint list consumer to a producer, sending “malicious” data to all other consumers on the topic. To prove this, kill the existing kafka-consume.sh command in the outpost-9999 window by typing control-C and instead run: through the /proc/sys/kernel/unprivileged_bpf_disabled sysctl knob. This is on purpose a one-time kill switch, meaning once set to 1, there is no option to reset it back to 0 until a new kernel reboot