Hi Gabriel,
Thanks for reporting the issue to us.
We have taken a look and we were able to reproduce the same. The issue is occurring since the default instance type of GKE "e2-medium" is not sufficient to schedule a Neo4j Pod . We had encountered a similar issue with the cluster and have updated the documentation to use --machine-type "e2-standard-2" as the minimum instance type required to successfully try out the example given in the documentation.
We are in the process of updating the same for NEO4J standalone GKE and you should see the changes very soon. Meanwhile , can you please try creating the GKE cluster using the below command and try the quickstart guide again
gcloud container clusters create my-neo4j-gke-cluster --num-nodes=1 --machine-type "e2-standard-2"
Once again , thanks for reporting the issue to us. We highly appreciate your time and effort.
Thanks,
Harshit