empire-backup : A secure backup facility located in Scarif [h�p://starwars.wikia.com/wiki/Scarif_vault] , which is allowed to “consume” from the secret deathstar-plans topic (label app=empire-backup). empire-outpost-8888 deployment "empire-outpost-8888" created deployment "empire-outpost-9999" created deployment "empire-backup" created Kubernetes will deploy the pods and service in the background. Running kubectl get svc 2181/TCP 2m NAME READY STATUS RESTARTS AGE empire-backup-6f4567d5fd-gcrvg 1/1 Running 0 2m empire-hq-59475b4b64-mrdww

deleted to prevent conflict behavior. Note Once aws-node DaemonSet is deleted, EKS will not try to restore it. kubectl -n kube-system delete daemonset aws-node Prepare & Deploy Cilium Note First, make empire-backup : A secure backup facility located in Scarif [http://starwars.wikia.com/wiki/Scarif_vault] , which is allowed to “consume” from the secret deathstar-plans topic (label app=empire-backup). empire-outpost-8888 deployment "empire-outpost-8888" created deployment "empire-outpost-9999" created deployment "empire-backup" created Kubernetes will deploy the pods and service in the background. Running kubectl get svc

empire-backup : A secure backup facility located in Scarif [http://starwars.wikia.com/wiki/Scarif_vault] , which is allowed to “consume” from the secret deathstar-plans topic (label app=empire-backup). empire-outpost-8888 deployment "empire-outpost-8888" created deployment "empire-outpost-9999" created deployment "empire-backup" created Kubernetes will deploy the pods and service in the background. Running kubectl get svc 2181/TCP 2m NAME READY STATUS RESTARTS AGE empire-backup-6f4567d5fd-gcrvg 1/1 Running 0 2m empire-hq-59475b4b64-mrdww

deleted to prevent conflict behavior. Note Once aws-node DaemonSet is deleted, EKS will not try to restore it. kubectl -n kube-system delete daemonset aws-node Deploy Cilium Note First, make sure you should produce messages to empire-announce or deathstar-plans (label app=empire-hq). empire-backup : A secure backup facility located in Scarif [https://starwars.fandom.com/wiki/Scarif_vault] , which is allowed allowed to “consume” from the secret deathstar-plans topic (label app=empire-backup). empire-outpost-8888 : A random outpost in the empire. It needs to “consume” messages from the empire-announce topic

deleted to prevent conflict behavior. Note Once aws-node DaemonSet is deleted, EKS will not try to restore it. kubectl -n kube-system delete daemonset aws-node Deploy Cilium Note First, make sure you the Cilium docker image and Cilium CLI tool: docker rm -f cilium sudo rm /usr/bin/cilium Then restore the domain name resolver configuration: sudo cp /etc/resolv.conf.orig /etc/resolv.conf sudo systemctl should produce messages to empire-announce or deathstar-plans (label app=empire-hq). empire-backup : A secure backup facility located in Scarif [https://starwars.fandom.com/wiki/Scarif_vault] , which is allowed

should produce messages to empire-announce or deathstar-plans (label app=empire-hq). empire-backup : A secure backup facility located in Scarif [https://starwars.fandom.com/wiki/Scarif_vault] , which is allowed allowed to “consume” from the secret deathstar-plans topic (label app=empire-backup). empire-outpost-8888 : A random outpost in the empire. It needs to “consume” messages from the empire-announce topic deployment "empire-outpost-8888" created deployment "empire-outpost-9999" created deployment "empire-backup" created Kubernetes will deploy the pods and service in the background. Running kubectl get svc

should produce messages to empire-announce or deathstar-plans (label app=empire-hq). empire-backup : A secure backup facility located in Scarif [https://starwars.fandom.com/wiki/Scarif_vault] , which is allowed allowed to “consume” from the secret deathstar-plans topic (label app=empire-backup). empire-outpost-8888 : A random outpost in the empire. It needs to “consume” messages from the empire-announce topic deployment "empire-outpost-8888" created deployment "empire-outpost-9999" created deployment "empire-backup" created Kubernetes will deploy the pods and service in the background. Running kubectl get svc