Cloud-native applications, known as CNA 1.0 in this book, typically operate on well-architected platforms with decentralized management. However, they are precisely ruled by GitOps-enabled policies and manifests. Consider the performances of the Berlin Philharmonic in the Berlin Philharmonie Hall under the baton of Sir Simon Rattle. It's not uncommon for a few players to be absent on any given night, substituted seamlessly by others. Even section leaders, such as the principal violist or principal cellist, may change due to unforeseen circumstances like illness. As seasoned classical concert attendees, we rarely notice any decline in the quality of the performances. How is this possible? It's thanks to the orchestra's high operational excellence and maturity, as well as the loosely coupled nature of the repertoire and the musicians. As long as the concertmaster and the conductor are present, the show maintains the same high standard as the previous night. This mirrors the scenario with cloud-native applications and platforms. eBPF, instrumentation, and signals are just melodies, observability is the symphony. Microservices can be redeployed, upgraded, and transformed, yet the product and SLAs remain consistent with the promises made by the product manager and SRE team.