<p>Is it advisable to use a normal Google Cloud Load Balancer pointing to my Kubernetes services? </p>

<p>I'm new to Kubernetes and I feel way more familiarized with the way normal Google Cloud Balancers are configured.</p>

Guillermo
<p>There's nothing wrong with it AFAIK, though people with more Kubernetes experience than GCP/Terraform/... might find it a little unusual.</p>

<p>See the discussion of <a href="https://kubernetes.io/docs/concepts/services-networking/service/#loadbalancer" rel="nofollow noreferrer">LoadBalancer type services</a> in the Kubernetes documentation for some background.  In particular, this notes for LoadBalancer services</p>

<blockquote>
  <p><code>NodePort</code> and <code>ClusterIP</code> Services, to which the external load balancer routes, are automatically created.</p>
</blockquote>

<p>You can do the same thing by hand if you'd like: create a NodePort type service, then create an external load balancer that routes to that exposed port on any or all nodes.  Keeping track of the list of nodes is a potential issue, and you either need to statically assign <code>nodePort:</code> values or find them after services are created.</p>

<p>Depending on how your organization is structured, even if a development team can deploy their own code into the cluster, you'll probably require your operations team to set up the external load balancer, which could be either good ("governance") or bad ("inflexible").</p>
