I remember when load balancing was a case of setting up apache or nginx on a server and letting it handle the upstream connections.
This article is talking about routing traffic from a single IP globally to multiple backend Kubernetes clusters that can be running in any region. Traffic will automatically go to the closest region (with available capacity) or otherwise fallback to other endpoints, while also bypassing much of the Kubernetes network stack to go straight to the running pods via GCP's software-defined network.
The complexity here is warranted if you need the flexibility and features. If you don't then you can just stick with nginx.