eBPF Summit October 28, 2020 Debugging Go in production using eBPF ABOUT ME ? i’m Zain @zainasgar Co-Founder/CEO Pixie (@pixie_run) & Adjunct Professor of CS @ Stanford DEVELOPER PROBLEM You’re Argument Tracer ● Utilizing tracepoints for dynamic logging allows for easy instrumentation of production binaries ● The complexities of the Go ABI make it difficult to do. Especially when you consider:

changed drastically. The “benevolent dictator for life” of any given codebase is being replaced with a team of developers who have to collaborate on a codebase to move it forward. Instead of a single developer these tools and resources that eliminate obstacles. Developers should not have to file a list of support tickets and wait forever to get what they need. It’s a good idea to have a consistent process in application development teams that build features and release code into production. Platform teams, on the other hand, exist to support application development teams and make resources available to them whenever

August 2019, and I was making an internal move at Red Hat from the Ansible team to the OpenShift (Red Hat’s Kubernetes product) team. That was when I was introduced to Christian Hernandez. A font of Kubernetes Kubernetes knowledge, Christian would take the lead on building out some of the most complex systems our team could develop. Not only that, he saw a lot of potential for Kubernetes and was looking for ways pandemic. Meeting customers one-by-one via the communication platform du jour wasn’t scalable. Our team started live streaming, and on October 9, 2020, Christian and I hosted our first stream about GitOps

CPM4OSSP 083 CTinspector 084 eggo 085 nvwa 087 PilotGo 088 SysCare 090 5 Developer Support 092 Infrastructure 093 Compass-CI 093 CVE Manager 095 EUR 097 oepkgs 098 openEuler Software comes from the openEuler community. However, the software package release quality and maintenance support requirements of the openEuler community cannot be fully met due to the package quality, technical Innovation Projects openEuler Open Source OS Architecture Cloud Edge/KubeEdge Developer support Scenario collaboration Scenario enablement Linux kernel x86, Arm, RISC-V GPU NPU Real-time

leadership, a well-informed program office, and a cohesive and committed government and contractor team, Agile could enable the DoD to deliver IT capabilities faster and more effectively than traditional growing number of programs continue to chart new paths in this field. This guide is intended to support that growth, as well as to capture the best practices and lessons learned by these early Agile adopters execution will take time, trial and error, and shaping of processes, policies, and culture, but with support from oversight and process owners can reach the full potential of Agile development. Agile Acquisition

approach for rollbacks. At the time of writing, however, the present GitOps tools have very little support and guidance on how you perform a rollback in a standard way. Observability for GitOps (and Git) important to remember that some of the most useful questions in a software team are the following: ● Does our production environment contain feature X? ● Has feature X cleared our staging environment environment? ● Are bugs X, Y present only in staging or also in production as well? These kinds of questions are pretty important for most product owners and project managers and finding an answer

features enabled. These features may include unreleased or beta features that are not considered production-ready. While it provides a convenient way to try out experimental features, It should only be used Cilium on K3s [https://k3s.io/], a highly available, certified Kubernetes distribution designed for production workloads in unattended, resource-constrained, remote locations or inside IoT appliances. This with ARM support planned [https://github.com/cilium/cilium/issues/9898] for a future release. Install a Master Node The first step is to install a K3s master node making sure to disable support for the

CREATION OF DEV, TEST, AND PRODUCTION ENVRIONMENTS i. Major contributing cause of issues stems from releases representing the first time we see how an application behaves in a production-like environment ii documentation, procedures, etc. 7. Application configuration files 8. This also includes pre-production and build processes 9. Tools iv. 2014 State of DevOps Report – use of version control by Ops Routinely kill and replace production instances v. Keep developers’ environments most current e. MODIFY OUR DEFINITION OF DEVELOPMENT “DONE” TO INCLUDE RUNNNING IN PRODUCTION-LIKE ENVIRONMENTS i. In

Kubernetes Integration Multi-Cluster (Cluster Mesh) Getting Help FAQ Slack GitHub Training Enterprise support Security Bugs Operations System Requirements Summary Linux Distribution Compatibility Matrix Linux environment Self-Managed Kubernetes Managed Kubernetes Installer Integrations CNI Chaining Setting up Support for External Workloads (beta) Network Policy Security Tutorials Identity-Aware and HTTP-Aware Policy features enabled. These features may include unreleased or beta features that are not considered production-ready. While it provides a convenient way to try out experimental features, It should only be used

equipment for monitoring 1. Create telemetry in application & environments (to include production, pre-production, and CD pipeline) iii. Ian Malpass, Etsy – “If Engineering at Etsy has a religion, it’s the systems being monitored.” c. CREATE APPLICATION LOGGING TELEMETRY THAT HELPS PRODUCTION i. Dev & Ops create production telemetry as part of their daily workii. If it was important enough for an engineer engineer to implement, it is certainly important enough to generate enough production telemetry so that we can confirm that is it operating as designed and outcomes are being achieved. iii. Logging Levels