If you, like me, have recently migrated a service to a Kubernetes cluster using Istio, and now, out of the blue you find yourself fighting with never seen before 503 and/or 504, you may just need to tweak a couple of parameters to fix the issue.
ArgoCD and Istio are two powerful and well know projects in the kubernetes space. Making them playing nicely together though, can be a complicated tasks. Some of the well known challenges are cross project manifest dependency and independent kubernetes objects lifecycle that prevent CD tools to properly compute the logical health status of some kubernetes resources. In this blog post I’m going to show how to bootstrapp a Kubernetes cluster with ArgoCD and Istio.