Run Next.js Apps on Kubernetes/GKE (Bonus: GitHub CI/CD!)

[@tonmoy7203]

Thank you so much ❤❤❤❤

[@cheftimbob]

Thanks, this was so helpful as there's such a lack of current guidance on working with autopilot, github actions, and ci/cd. I have two questions regarding port mappings and paths. If the api routes on say /api/* at port 3000, I don't see this mapping if provided. Where would the custom mappings be configured? If you were going to have a websocket running on port 3001 at /, you would just add another port to the service configuration in resources.yaml?

[@erwanriou1]

Is there performance benefices for nextjs to run a gce balancer instead of an nginx one?

[@nodematic]

There are a few: 1) The GCE load balancer uses Google's global network, which extends to edge locations very close to the user, so more of the traffic between the user and your application is on Google Cloud's backbone (fast) instead of the public internet (slower). 2) The GCE load balancer is a serverless, scalable, managed service - so it's like having an unlimited-power Nginx. If you run your own Nginx (e.g., via a Kubernetes ingress controller), your CPU, RAM, and bandwidth resources will be more constrained. 3) If you decide to add CDN caching for performance, Cloud Armor for security, etc. - that'll be easy to do at Google Cloud's edge with the GCE load balancer, but not possible to do with the Nginx path. These will all be small improvements though. If you run the Nginx system well, the user experience will be similar in both cases. Here are a few videos on Nginx in GKE, if you're interested: * kzbin.info/www/bejne/mIesiXR7pdGMjMk * kzbin.info/www/bejne/eJ-ldIqtrpKar5I * kzbin.info/www/bejne/e3jEm6Roh9qYd7c * kzbin.info/www/bejne/nXnKinRtqp6KkLM

[@erwanriou1]

@@nodematic Yeah that make sens indeed. I was currently using an nginx topped by cloudflare CDN but i was wondering about the scaling performances.