Kubernetes’ Dirty Endpoint Secret And Ingress

At Ravelin we’ve migrated to Kubernetes (on GKE). This has been very successful. We’ve got pod disruption budgets coming out of our ears, our statefulsets are very stately, and rolling node replacements run without a hitch. The last piece of the puzzle is to move our API layer from the old VMs into our kubernetes cluster. For this we need to set up an Ingress so the API can be accessed from the outside world. At first this seems straight-forward. We just define the ingress controller, tinker with terraform to get some IP addresses and Google takes care of nearly everything else. And it all works like magic. Great! But we begin to notice our integration tests are occasionally receiving 502 errors. And there begins a journey that I’ll save you the pain of reading about by cutting directly to the final conclusions.


Be the first to comment !

Related Posts

8 months, 1 week ago


The polyglot, cloud-native programming language for zero-DevOps deployments into Kubernetes.


8 months, 1 week ago

Gitlab And Google Webcast - Running Containerized Applications on Modern Serverless Platforms

In this webcast, we'll walk through some of the benefits and challenges of using cloud-vendor-spe..

Jérôme Petazzoni , 8 months, 2 weeks ago

Kubernetes Deployments: The Ultimate Guide

One of the first Kubernetes commands that we learn and use is kubectl run. Folks who have experie..

Sandor Magyari , 9 months, 1 week ago

A deep dive into Kubernetes federation v2

One of the key features of our container management platform, Pipeline, and our CNCF certified Ku..

Carlos Arilla , 9 months, 3 weeks ago

How to Monitor Golden Signals in Kubernetes.

What are Golden signals metrics? How do you monitor golden signals in Kubernetes applications? Go..

9 months, 1 week ago


A Kubernetes controller to watch changes in ConfigMap and Secrets and then restart pods for Deplo..