create: VPC with 2 public and private subnets Bastion Hosts and NAT Gateways in the Public Subnet Three of each (masters, etcd, and worker nodes) in the Private Subnet AWS ELB in the Public Subnet for accessing operating correctly we can deploy our demo application. In our Star Wars-inspired example, there are three microservices applications: deathstar, tiefighter, and xwing. The deathstar runs an HTTP webservice Deployment [https://kubernetes.io/docs/concepts/workloads/controllers/deployment/] for each of the three services. Each deployment is identified using the Kubernetes labels (org=empire, class=deathstar)

create: VPC with 2 public and private subnets Bastion Hosts and NAT Gateways in the Public Subnet Three of each (masters, etcd, and worker nodes) in the Private Subnet AWS ELB in the Public Subnet for accessing forcing each external workload to be reconfigured to be able to connect to your cluster. There are two ways to get around this. You can enable a cluster job to create TLS secrets instead. This way the CA cert operating correctly we can deploy our demo application. In our Star Wars-inspired example, there are three microservices applications: deathstar, tiefighter, and xwing. The deathstar runs an HTTP webservice

create: VPC with 2 public and private subnets Bastion Hosts and NAT Gateways in the Public Subnet Three of each (masters, etcd, and worker nodes) in the Private Subnet AWS ELB in the Public Subnet for accessing operating correctly we can deploy our demo application. In our Star Wars-inspired example, there are three microservices applications: deathstar, tiefighter, and xwing. The deathstar runs an HTTP webservice Deployment [https://kubernetes.io/docs/concepts/workloads/controllers/deployment/] for each of the three services. Each deployment is identified using the Kubernetes labels (org=empire, class=deathstar)

create: VPC with 2 public and private subnets Bastion Hosts and NAT Gateways in the Public Subnet Three of each (masters, etcd, and worker nodes) in the Private Subnet AWS ELB in the Public Subnet for accessing operating correctly we can deploy our demo application. In our Star Wars-inspired example, there are three microservices applications: deathstar, tiefighter, and xwing. The deathstar runs an HTTP webservice Deployment [https://kubernetes.io/docs/concepts/workloads/controllers/deployment/] for each of the three services. Each deployment is identified using the Kubernetes labels (org=empire, class=deathstar)

create: VPC with 2 public and private subnets Bas�on Hosts and NAT Gateways in the Public Subnet Three of each (masters, etcd, and worker nodes) in the Private Subnet AWS ELB in the Public Subnet for opera�ng correctly we can deploy our demo applica�on. In our Star Wars-inspired example, there are three microservices applica�ons: deathstar, �efighter, and xwing. The deathstar runs an HTTP webservice Deployment [h�ps://kubernetes.io/docs/concepts/workloads/controllers/deployment/] for each of the three services. Each deployment is iden�fied using the Kubernetes labels ( org=empire, class=deathstar )

create: VPC with 2 public and private subnets Bastion Hosts and NAT Gateways in the Public Subnet Three of each (masters, etcd, and worker nodes) in the Private Subnet AWS ELB in the Public Subnet for accessing operating correctly we can deploy our demo application. In our Star Wars-inspired example, there are three microservices applications: deathstar, tiefighter, and xwing. The deathstar runs an HTTP webservice Deployment [https://kubernetes.io/docs/concepts/workloads/controllers/deployment/] for each of the three services. Each deployment is identified using the Kubernetes labels (org=empire, class=deathstar)

create: VPC with 2 public and private subnets Bastion Hosts and NAT Gateways in the Public Subnet Three of each (masters, etcd, and worker nodes) in the Private Subnet AWS ELB in the Public Subnet for accessing operating correctly we can deploy our demo application. In our Star Wars-inspired example, there are three microservices applications: deathstar, tiefighter, and xwing. The deathstar runs an HTTP webservice Deployment [https://kubernetes.io/docs/concepts/workloads/controllers/deployment/] for each of the three services. Each deployment is identified using the Kubernetes labels (org=empire, class=deathstar)

in production How does it work? – Adds ~20ns of overhead per run Two ways to enable kernel eBPF stats sysctl procfs Three ways to access kernel eBPF stats bpftool prog show bpf syscall BPF_OBJ_GET_INFO_BY_FD