One of the first things I usually do after spinning up a GKE cluster is to secure HTTP traffic to backends by setting up an API Gateway called KrakenD. In addition to security, we can use KrakenD to route traffic to different namespaces since GKE’s Ingress doesn’t allow for routing across namespaces at this stage.
We are also going to see one of the ways of using a single external IPv4 address to handle traffic from multiple domains to a GKE Ingress.
Non-existent domains of
some.domain.io will be used throughout this guide. …
Lead Engineer. Based in Tāmaki Makaurau, Aotearoa (Auckland, New Zealand).