<p>When I create a LoadBalancer like this:</p>
<pre><code>apiVersion: v1
kind: Service
metadata:
  name: webhook-event-source-service
  namespace: argo-events
  annotations:
    networking.gke.io/load-balancer-type: &quot;Internal&quot;
spec:
  type: LoadBalancer
  loadBalancerIP: 10.196.xxx.xxx
  selector:
    controller: eventsource-controller
  ports:
  - port: 1212
    targetPort: 1212
    protocol: TCP
</code></pre>
<p>Why does the GKE Console list it as an &quot;External Load Balancer&quot;?</p>
<p><a href="https://i.stack.imgur.com/FqobF.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/FqobF.png" alt="enter image description here" /></a></p>

Raffael
<p>In fact, this problem has already been reported some time ago on Google's <a href="https://issuetracker.google.com/issues/179694570" rel="nofollow noreferrer">public issue tracker</a> and it's currently under investigation:</p>
<blockquote>
<p>Problem you have encountered:</p>
<p>I created a Deployment and a LoadBalancer Service as described in the
<a href="https://cloud.google.com/kubernetes-engine/docs/how-to/internal-load-balancing" rel="nofollow noreferrer">official
docs</a></p>
<p>Notice the LoadBalancer service is annotated with
<code>networking.gke.io/load-balancer-type: &quot;Internal&quot;</code></p>
<p>What you expected to happen:</p>
<p>I expected to see this service listed as  <code>Internal Load Balancer</code>  in
the  <code>Services &amp; Ingress</code>  view of the GCP console.</p>
<p>Instead it is listed as an  <code>External Load Balancer</code>. (See attachment)</p>
<p>Going to the specific load balancer in the  <code>Load Balancing</code>  view
shows it as Internal.</p>
<p>Steps to reproduce:</p>
<p>Just follow the docs and head to the  <code>Services &amp; Ingress</code>  view in
the console.</p>
</blockquote>
<p>And the answer from <strong>GCP support</strong>, confirming that they were also able to reproduce the issue and are analyzing it at the moment:</p>
<blockquote>
<p>Hello,</p>
<p>Thank you for reaching out.</p>
<p>I've managed to reproduce the same scenario that you've included in
your message.</p>
<p>I forwarded this information to the Engineering team.</p>
<p>Please follow this issue in case of any further updates.</p>
<p>Best regards</p>
</blockquote>
<p>So if you are interested in progressing on this issue, feel free to follow <a href="https://issuetracker.google.com/issues/179694570" rel="nofollow noreferrer">this thread</a> for further updates.</p>
