As part of the Platform team we adhere to the GitOps principles and manage our cloud-native deployments of our platform accordingly. In turn, it is a challenge to develop new tools for observability along with experimenting with new deployment; components, topologies and configurations in them being production-ready from the get go. However, as per how the life-cycle is managed by GitOps tools (ArgoCD in our case) the pay-off is substantial for managing multiple environments. To this end, we require ephemeral kubernetes clusters that center around as per the various required levels of isolation. Additionally, the helm templating at its baseline (especially for our observability stack for ) for complex configurations require the addition of various workarounds that builds a level of technical debt which led us to switch to the use of CDK8s (Cloud Development Kit for Kubernetes) in taking a programmatic approach as opposed to imperative one.
The scope of this session focuses on how we configure and utilize these ephemeral environments in experimenting with microservices that integrate with Multiple Pulsar Clusters and how we develop our Observability Stack that is build-out to handle High-Cardinality labels for Metrics, Logging and Tracing in Monitoring it within the same setup for a Telco Orchestration Platform that uses Apache Pulsar as its event fabric.
This Session recording was originally presented at Pulsar Summit North America 2023.