Azure resources (resource groups, networks, etc.) specifically for this tutorial, the following commands (borrowed from the AKS documentation) run as a script or manually all in the same terminal are sufficient --network-plugin azure Configure kubectl to Point to Newly Created Cluster Run the following commands to configure kubectl to connect to this AKS cluster: az aks get-credentials --resource-group $RESOURCE_GROUP_NAME kops Setting up IAM Group and User Assuming you have all the prerequisites, run the following commands to create the kops user and group: # Create IAM group named kops and grant access aws iam create-group

kops Setting up IAM Group and User Assuming you have all the prerequisites, run the following commands to create the kops user and group: # Create IAM group named kops and grant access aws iam create-group core@public_ip_of_bastion_host Execute the commands below from the bas�on host. If kubectl isn’t installed on the bas�on host, you can login to the master node to test the below commands. You may need to copy the private rules enforced, both xwing and �efighter will be able to request landing. To test this, use the commands below. $ kubectl exec xwing -- curl -s -XPOST deathstar.default.svc.cluster.local/ Ship landed

available. If you require Azure IPAM, refer to the AKS (Azure IPAM) installation. The following commands create a Kubernetes cluster using Azure Kubernetes Service [https://docs.microsoft.com/en-us/azure/aks/] kops Setting up IAM Group and User Assuming you have all the prerequisites, run the following commands to create the kops user and group: $ # Create IAM group named kops and grant access $ aws iam create-group core@public_ip_of_bastion_host Execute the commands below from the bastion host. If kubectl isn’t installed on the bastion host, you can login to the master node to test the below commands. You may need to copy the private

the namespace in which Cilium is installed as CILIUM_NAMESPACE environment variable. Subsequent commands reference this environment variable. export CILIUM_NAMESPACE=kube-system Install Hubble Hubble the namespace in which Cilium is installed as CILIUM_NAMESPACE environment variable. Subsequent commands reference this environment variable. export CILIUM_NAMESPACE=kube-system Install Hubble Hubble the namespace in which Cilium is installed as CILIUM_NAMESPACE environment variable. Subsequent commands reference this environment variable. export CILIUM_NAMESPACE=kube-system Install Hubble Hubble

to create a Kubernetes cluster locally or using a managed Kubernetes service: GKE The following commands create a Kubernetes cluster using Google Kubernetes Engine [https://cloud.google.com/kubernetes-engine] available. If you require Azure IPAM, refer to the AKS (Azure IPAM) installation. The following commands create a Kubernetes cluster using Azure Kubernetes Service [https://docs.microsoft.com/en-us/azure/aks/] require Azure IPAM, we recommend you to switch to the AKS (BYOCNI) installation. The following commands create a Kubernetes cluster using Azure Kubernetes Service [https://docs.microsoft.com/en-us/azure/aks/]

experience Kubernetes service load-balancing issues, then set [https://minikube.sigs.k8s.io/docs/commands/config/] any other driver from the supported list [https://minikube.sigs.k8s.io/docs/drivers/]. the namespace in which Cilium is installed as CILIUM_NAMESPACE environment variable. Subsequent commands reference this environment variable. export CILIUM_NAMESPACE=kube-system Enable Hubble for Cluster-Wide tar.gz SHA256 type hubble-windows-amd64.tar.gz.sha256sum :: verify that the checksum from the two commands above match tar zxf hubble-windows-amd64.tar.gz and move the hubble.exe CLI to a directory listed

the namespace in which Cilium is installed as CILIUM_NAMESPACE environment variable. Subsequent commands reference this environment variable. export CILIUM_NAMESPACE=kube-system Enable Hubble Hubble tar.gz SHA256 type hubble-windows-amd64.tar.gz.sha256sum :: verify that the checksum from the two commands above match tar zxf hubble-windows-amd64.tar.gz and move the hubble.exe CLI to a directory listed HUBBLE_DEFAULT_SOCKET_PATH=localhost:4245 This will allow you to use hubble status and hubble observe commands without having to specify the server address via the --server flag. (Distributed mode only) To

skies, asteroids, and dust, The Silver Lining flew between the nebulae. On the front deck, at the commands, was Captain Tux, Who carried passengers across the galaxy. While the crew, hard at work, assisted Let’s meet the passengers!” The Silver Lining’s passengers had long been complaining They couldn’t send messages in their own encoding. When the bees jumped on the case, it marked the beginning Of a whole

nmap-ncat $ nc -4kle /bin/cat 127.0.0.1 7777 & [1] 1289 $ ss -4tlpn sport = 7777 State Recv-Q Send-Q Local Address:Port Peer Address:Port Process LISTEN 0 10 127.0.0.1:7777 0.0.0 echo_socket map $ nc -4kle /bin/cat 127.0.0.1 7777 & [1] 1289 $ ss -tlpne 'sport = 7777' State Recv-Q Send-Q Local Address:Port Peer Address:Port Process LISTEN 0 10 127.0.0.1:7777 0.0.0

CiliumNetworkPolicies Layer 7 HTTP Filtering Outbound to DNS Name Clusterwide Policy 14 Cilium CLI commands Listing Endpoints on a Node Traffic Denied by Policy Traffic Allowed by Policy 15 Hubble Benefits