Infrastructure 3.0: Load balancing, observability, and deployments

Gard Rimestad's article provides an update on Unleash's infrastructure, focusing on improvements in load balancing, observability, and deployment processes following their transition from VMs to Kubernetes. The team addressed challenges with Traefik load balancer pods timing out by adjusting their Kubernetes service configuration to better synchronize with AWS Network Load Balancers, ultimately opting to expose Traefik through host ports for more reliable traffic routing. In terms of observability, they shifted from direct Cloudwatch logging to using Fluent Bit, Loki, and S3 for efficient log management and implemented VictoriaMetrics for enhanced metrics collection. For deployments, Unleash optimized their approach by dividing the deployment responsibilities among different operators, significantly speeding up customer updates and reducing the burden on developers. Looking ahead, they are exploring the use of Spot instances and developing a Kubernetes drain assistant to enable the integration of Karpenter for autoscaling and resource optimization.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.