CREATED MIN SIZE MAX SIZE DESIRED CAPACITY INSTANCE TYPE IMAGE ID test-cluster ng-25560078 2019-07-23T06:05:35Z 0 2 0 Values=hvm" "Name=name,Values=CoreOS- stable*" --query 'sort_by(Images,&CreationDate)[-1].{id:ImageLocation}' { "id": "595879546273/CoreOS-stable-1745.5.0-hvm" } Creating a Cluster Note that you will infrastructure. Configure AWS credentials Export the variables for your AWS credentials export AWS_ACCESS_KEY_ID="www" export AWS_SECRET_ACCESS_KEY ="xxx" export AWS_SSH_KEY_NAME="yyy" export AWS_DEFAULT_REGION="zzz"

command below. aws ec2 describe-images --region=us-west-2 --owner=595879546273 --filters { "id": "595879546273/CoreOS-stable-1745.5.0-hvm" } Creating a Cluster Note that you will need to specify infrastructure. Configure AWS credentials Export the variables for your AWS creden�als export AWS_ACCESS_KEY_ID="www" export AWS_SECRET_ACCESS_KEY ="xxx" export AWS_SSH_KEY_NAME="yyy" export AWS_DEFAULT_REGION="zzz" ‘cc_door_client’ with the name of the gRPC method to call, and any parameters (in this case, the door-id): $ kubectl exec terminal-87 -- python3 /cloudcity/cc_door_client.py GetName Door name is: Spaceport

from Install Cilium. However we’re enabling managed etcd and setting both cluster-name and cluster-id for each cluster. Make sure context is set to kind-cluster2 cluster. kubectl config use-context kind-cluster2 global.identityAllocationMode=kvstore \ --set global.cluster.name=cluster2 \ --set global.cluster.id=2 Change the kubectl context to kind-cluster1 cluster: kubectl config use-context kind-cluster1 global.identityAllocationMode=kvstore \ --set global.cluster.name=cluster1 \ --set global.cluster.id=1 Setting up Cluster Mesh We can complete setup by following the Cluster Mesh guide with Expose the

installation with minimal privileges over the AKS node resource group: AZURE_SUBSCRIPTION_ID=$(az account show --query "id" --output tsv) AZURE_NODE_RESOURCE_GROUP=$(az aks show --resource-group ${RESOURCE_GROUP} IPTION_ID}/resourceGroups/${AZURE_NODE_RES OURCE_GROUP} --role Contributor --output json --only-show-errors) AZURE_TENANT_ID=$(echo ${AZURE_SERVICE_PRINCIPAL} | jq -r '.tenant') AZURE_CLIENT_ID=$(echo GROUP \ --set azure.subscriptionID=$AZURE_SUBSCRIPTION_ID \ --set azure.tenantID=$AZURE_TENANT_ID \ --set azure.clientID=$AZURE_CLIENT_ID \ --set azure.clientSecret=$AZURE_CLIENT_SECRET \ --set

from Install Cilium. However we’re enabling managed etcd and setting both cluster-name and cluster-id for each cluster. Make sure context is set to kind-cluster2 cluster. kubectl config use-context kind-cluster2 managed=true \ --set identityAllocationMode=kvstore \ --set cluster.name=cluster2 \ --set cluster.id=2 Change the kubectl context to kind-cluster1 cluster: kubectl config use-context kind-cluster1 managed=true \ --set identityAllocationMode=kvstore \ --set cluster.name=cluster1 \ --set cluster.id=1 Setting up Cluster Mesh We can complete setup by following the Cluster Mesh guide with Expose the

from Install Cilium. However we’re enabling managed etcd and setting both cluster-name and cluster-id for each cluster. Make sure context is set to kind-cluster2 cluster. kubectl config use-context kind-cluster2 global.identityAllocationMode=kvstore \ --set global.cluster.name=cluster2 \ --set global.cluster.id=2 Change the kubectl context to kind-cluster1 cluster: kubectl config use-context kind-cluster1 global.identityAllocationMode=kvstore \ --set global.cluster.name=cluster1 \ --set global.cluster.id=1 Setting up Cluster Mesh We can complete setup by following the Cluster Mesh guide with Expose the

installation with minimal privileges over the AKS node resource group: AZURE_SUBSCRIPTION_ID=$(az account show --query "id" --output tsv) AZURE_NODE_RESOURCE_GROUP=$(az aks show --resource-group ${RESOURCE_GROUP} IPTION_ID}/resourceGroups/${AZURE_NODE_RES OURCE_GROUP} --role Contributor --output json --only-show-errors) AZURE_TENANT_ID=$(echo ${AZURE_SERVICE_PRINCIPAL} | jq -r '.tenant') AZURE_CLIENT_ID=$(echo GROUP \ --set azure.subscriptionID=$AZURE_SUBSCRIPTION_ID \ --set azure.tenantID=$AZURE_TENANT_ID \ --set azure.clientID=$AZURE_CLIENT_ID \ --set azure.clientSecret=$AZURE_CLIENT_SECRET \ --set

btf_id 32 build the prog load & pin the prog Pin BPF maps used by echo_dispatch # mount -t bpf none ~vagrant/bpffs # sudo chown vagrant.vagrant ~vagrant/bpffs # bpftool map show id 28 28: hash bpftool map pin id 28 ~vagrant/bpffs/echo_ports # bpftool map show id 29 29: sockmap name echo_socket flags 0x0 key 4B value 8B max_entries 1 memlock 4096B # bpftool map pin id 29 ~vagrant/bpffs/echo_socket

#include struct stack_key_t { int pid; char name[16]; int user_stack_id; int kernel_stack_id; }; BPF_STACK_TRACE(stack_traces, 16384); BPF_HASH(counts, struct stack_key_t, uint64_t); 32; bpf_get_current_comm(&key.name, sizeof(key.name)); key.kernel_stack_id = stack_traces.get_stackid(ctx, 0); key.user_stack_id = stack_traces.get_stackid(ctx, BPF_F_USER_STACK); u64 zero = 0,

skb_csum_hwoffload_help (len: 5764 gso_type: tcpv4) Functions the packets have gone through CPU ID Time Stamp User defined tracing data (with Lua script) … Use case • Multi tenant HV networking