The article discusses the author's experience with presenting OpenTelemetry demos to varied audiences and the constant updates made to keep presentations engaging.
After a job loss due to an IT crisis, the author joined LoftLabs, working on vCluster, a cluster virtualization solution.
The demo underwent changes focusing on Kubernetes-related features, transitioning from Docker Compose to Helm for more intricate workload deployments.
Helm subcharts like Valkey, Traefik, Jaeger, PostgreSQL, and the OpenTelemetry components were utilized to optimize infrastructure setup.
The article highlights design choices, including using Traefik as an Ingress Controller and segmenting Docker Compose services into infrastructure and app groups.
Configuring access between host and virtual clusters, leveraging Traefik, and integrating OpenTelemetry Collector to monitor clusters are discussed.
The author details deploying and initializing PostgreSQL with scripts, utilizing Helm charts efficiently, and exploring Kubernetes instrumentation with OpenTelemetry.
A Quarkus component addition for showcasing OpenTelemetry integration and a summary of new features like Quarkus, vCluster, Helm usage, etc., are included.
The article concludes with a call for feedback and mentions missing components like .Net, showcasing a commitment to continuous improvement and expansion.
For more details, the article suggests exploring topics like Helm, OpenTelemetry Collector, Kubernetes auto-instrumentation, vCluster, Traefik, and Quarkus usage.
The author invites suggestions and contributions, embracing a collaborative approach for further enhancements in the tech landscape.