Using BCC and bpftrace with Performance Co-Pilot Andreas Gerstmayr October 28, 2020 Source: https://pcp.io https://github.com/iovisor/bcc https://bpftrace.org 2 eBPF Compiler Collection bpftrace bpftrace BCC high-level tracing language for eBPF Performance Co-Pilot system performance analysis toolkit Performance Co-Pilot 3 Toolkit for collecting, analyzing, visualizing and responding to the

list in one of the Cilium pods and validate that all nodes are discovered correctly. If the node discovery is not working, run cilium kvstore get --recursive cilium/state/nodes/v1/ and check if an entry variant of Pilot to inject the Cilium network policy filters into each Is�o sidecar proxy: $ curl -s https://raw.githubusercontent.com/cilium/cilium/v1.5/examples/ku $ awk -f cilium-pilot.awk \ < ${ISTIO_HOME}/install/kubernetes/helm/istio/charts/pilot/templates/ > istio-cilium-helm/charts/pilot/templates/deployment.yaml Configure the Is�o’s sidecar injec�on to setup the transparent

recovery) DEEP INSIGHTS Plan to Support metrics, alerts, log processing and workload analysis AUTO PILOT Plan to Support horizontal/vertical scaling, auto config tuning, abnormal detection, schedule tuningCloud

as they could easily configure new resources in minutes to meet the surge in demand. During the pilot stage, the evaluating product team discovered that they were able to operate their entire stack with

and can view the resulting calculations for the loan-repayment amount or the interest rate. • Data Pilot: Enables you to compare, combine and arrange large amounts of data. It helps you pull in raw data databases, cross-tabulate, summarise and convert the data into meaningful information. You can use Data Pilot to create interactive tables, which allows the data to be frequently arranged, rearranged or summarised

Cilium pods and validate that it lists both local nodes and nodes from remote clusters. If this discovery does not work, validate the following: In each cluster, check that the kvstore contains information Proxy (preferred) 1. Update existing policies to intercept DNS requests. See DNS Policy and IP Discovery or the example above 2. Allow pods to make DNS requests to populate the cilium-agent cache. To {"apiKey": "produce", "topic": "empire-announce"} ] } }] }] }] DNS Policy and IP Discovery Policy may be applied to DNS traffic, allowing or disallowing specific DNS query names or patterns

Cilium pods and validate that it lists both local nodes and nodes from remote clusters. If this discovery does not work, validate the following: In each cluster, check that the kvstore contains information {"apiKey": "produce", "topic": "empire-announce"} ] } }] }] }] DNS Policy and IP Discovery Policy may be applied to DNS traffic, allowing or disallowing specific DNS query names or patterns kernel modules. https://sourceware.org/git/gitweb.cgi?p=systemtap.git;a=summary PCP Performance Co-Pilot (PCP) is a system performance and analysis framework which is able to collect metrics through a variety

BGP (beta) Egress Gateway (beta) Cluster Mesh Setting up Cluster Mesh Load-balancing & Service Discovery Network Policy Setting up Support for External Workloads (beta) Operations Running Prometheus kube-dns and kubernetes have the required label value. Neighbor Discovery When kube-proxy replacement is enabled Cilium does L2 neighbor discovery of nodes in the cluster. In some rare cases Cilium may leave Cilium from performing the neighbor discovery and instead rely on the Linux kernel to discover hosts on the same L2 network you can pass the --enable-l2-neigh- discovery=false flag to the cilium-agent. However

Cilium pods and validate that it lists both local nodes and nodes from remote clusters. If this discovery does not work, validate the following: In each cluster, check that the kvstore contains information {"apiKey": "produce", "topic": "empire-announce"} ] } }] }] }] DNS Policy and IP Discovery Policy may be applied to DNS traffic, allowing or disallowing specific DNS query names or patterns workload. Multi cluster: All state propagation between clusters depends on the kvstore. Node discovery: New nodes require to register themselves in the kvstore. Agent bootstrap: The Cilium agent will

(beta) CiliumEndpointSlice (beta) Cluster Mesh Setting up Cluster Mesh Load-balancing & Service Discovery Network Policy Setting up Support for External Workloads (beta) Operations Running Prometheus feature, set loadBalancer.serviceTopology=true. Neighbor Discovery When kube-proxy replacement is enabled, Cilium does L2 neighbor discovery of nodes in the cluster. This is required for the service Cilium 1.10 or earlier, the agent itself contained an ARP resolution library where it triggered discovery and periodic refresh of new nodes joining the cluster. The resolved neighbor entries were pushed