为什么 GKE Con​​sole 会将内部 LB 列为外部 LB？

Question

当我像这样创建 LoadBalancer 时：

apiVersion: v1
kind: Service
metadata:
  name: webhook-event-source-service
  namespace: argo-events
  annotations:
    networking.gke.io/load-balancer-type: "Internal"
spec:
  type: LoadBalancer
  loadBalancerIP: 10.196.xxx.xxx
  selector:
    controller: eventsource-controller
  ports:
  - port: 1212
    targetPort: 1212
    protocol: TCP

为什么 GKE 控制台将其列为“外部负载均衡器”？

Answer 1

其实这个问题早就在Google的public issue tracker上报道过，目前正在调查中：

Problem you have encountered:

I created a Deployment and a LoadBalancer Service as described in the official docs

Notice the LoadBalancer service is annotated with networking.gke.io/load-balancer-type: "Internal"

What you expected to happen:

I expected to see this service listed as Internal Load Balancer in the Services & Ingress view of the GCP console.

Instead it is listed as an External Load Balancer. (See attachment)

Going to the specific load balancer in the Load Balancing view shows it as Internal.

Steps to reproduce:

Just follow the docs and head to the Services & Ingress view in the console.

以及来自 GCP 支持 的回答，确认他们也能够重现该问题并目前正在对其进行分析：

Hello,

Thank you for reaching out.

I've managed to reproduce the same scenario that you've included in your message.

I forwarded this information to the Engineering team.

Please follow this issue in case of any further updates.

Best regards

因此，如果您有兴趣在这个问题上取得进展，请随时关注 this thread 以获取进一步的更新。