Crash loop of history service in K8s cluster

That was helpful. We have everything working - thanks for the assistance and tips.

For future readers - it turns out we did have an issue with our network cutting off connections via IP:port calls. We needed to add some headless services to get around istio.

2 Likes