Kubernetes
![A thumbnail image](https://developerzen.com/golden-testing-helm-charts/cover_hu8294fbff781a61a2e2fa25e2c7347df8_545125_0x290_resize_q75_h2_box_3.webp)
We love tests at Twingate. When working on the Twingate’s helm charts repository I wanted to incorporate testing like we do with other code.
![A thumbnail image](https://developerzen.com/zero-downtime-django-gunicorn-deployments-on-gke/cover_huf3202e060786fe0a14eea9d9ca75c5f2_484128_0x290_resize_q75_h2_box_3.webp)
We recently switched to Twingate’s GKE load balancer to use Google’s new Container-native load balancer. The premise was good - LB talks directly to pods and saves an extra network hops, (with classic LB, traffic goes from LB to a GKE node which then, based on iptables configured by kube-proxy, get routed to the pod) and should perform better, support more features, and in general we’d rather be on google’s maintained side and not on legacy tech.