[HN Gopher] What we learned after a year of GitLab.com on Kubern...
       ___________________________________________________________________
        
       What we learned after a year of GitLab.com on Kubernetes
        
       Author : ecliptik
       Score  : 21 points
       Date   : 2020-09-16 21:22 UTC (1 hours ago)
        
 (HTM) web link (about.gitlab.com)
 (TXT) w3m dump (about.gitlab.com)
        
       | t3rabytes wrote:
       | > Increased billing from cross-AZ traffic
       | 
       | Yep, we (Basecamp) have been bit by this with EKS too. By default
       | the ALB Ingress Controller will put all cluster nodes into the
       | target group and a request can hit kube-proxy in any AZ before
       | being directed to the right place, causing a lot of inter-AZ
       | traffic churn. It's mildly annoying.
       | 
       | (with alb-ingress-controller you can change target-type to IP to
       | have traffic go direct to pods that will actually back a given
       | service instead of via kube-proxy on a random node, but the big
       | fault there is that if alb-ingress-controller gets hung up on
       | something and you deploy, you can send traffic to nowhere because
       | the target group still has old IPs for pods that don't exist).
        
       | ishcheklein wrote:
       | We are using k8s as well for a project that we also provide on-
       | prem install too. We decided to use kustomize for now vs doing
       | helm for now. Curious, have someone had experience with both to
       | compare. What are the benefits of using helm?
        
       ___________________________________________________________________
       (page generated 2020-09-16 23:00 UTC)