<p>GKE uses the <a href="https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/#kubenet" rel="nofollow noreferrer">kubenet</a> network plugin for setting up container interfaces and configures routes in the VPC so that containers can reach eachother on different hosts.</p>

<p>Wikipedia defines an <a href="https://en.wikipedia.org/wiki/Overlay_network" rel="nofollow noreferrer">overlay</a> as <code>a computer network that is built on top of another network</code>.</p>

<p>Should GKE's network model be considered an overlay network? It is built on top of another network in the sense that it relies on the connectivity between the nodes in the cluster to function properly, but the Pod IPs are natively routable within the VPC as the routes inform the network which node to go to to find a particular Pod.</p>

dippynark
<p>VPC-native and non VPC native GKE clusters uses <a href="https://cloud.google.com/vpc/docs/overview" rel="nofollow noreferrer">GCP virtual networking</a>. It is not strictly an overlay network by definition. An overlay network would be one that's isolated to just the GKE cluster. </p>

<p>VPC-native clusters work like this: </p>

<p>Each node VM is given a primary internal address and two alias IP ranges.  One alias IP range is for pods and the other is for services. 
The GCP subnet used by the cluster must have at least two secondary IP ranges (one for the pod alias IP range on the node VMs and the other for the services alias IP range on the node VMs).</p>

<p>Non-VPC-native clusters:</p>

<p>GCP creates custom static routes whose destinations match pod IP space and services IP space.  The next hops of these routes are node VMs by name, so there is instance based routing that happens as a "next step" within each VM.  </p>

<p>I could see where some might consider this to be an overlay network. I don’t believe this is the best definition because the pod and service IPs are addressable from other VMs, outside of GKE cluster, in the network.</p>

<p>For a deeper dive  on GCP’s network infrastructure, <a href="https://www.usenix.org/system/files/conference/nsdi18/nsdi18-dalton.pdf" rel="nofollow noreferrer">GCP’s network virtualization whitepaper</a> can be found <a href="https://www.usenix.org/system/files/conference/nsdi18/nsdi18-dalton.pdf" rel="nofollow noreferrer">here</a>.</p>
