JWA Customization: Kubecost Response Error

[saffaalvi]

When the kubecost changes were brought into 1.3, on the dev cluster there is a 503 error from the cost response.
upstream connect error or disconnect/reset before headers. reset reason: connection termination
From what I've seen online, this might have something to do with Istio.

Not sure if the kubecost service is even supposed to be working on dev?

cc @sylus

[sylus]

It seems someone manually deployed a bad image?

I set the SHA back to 813f13a and it works fine now

[Jose-Matsuda]

We manually deployed an image that we built on Saffa's branch to check and fix for a different error that appeared when opening up the console.

[sylus]

Ok i finally found some time ^_^ so oddly i wasn't seeing it earlier in the day but the container image is the same as was reverted to and i see this problem now.

I put the SHA for the latest commit 708d307

The service is up for cost-analyzer and the end points are correct so this requires some further investigation.

[sylus]

This was a network policy that needed to be updated it should be fixed now.

[zachomedia]

https://github.com/StatCan/aaw-network-policies/commit/af17a3c3c7417cd91acab0cbc1447535c8f406d0 was the change (the labels changed on the jupyter web app pod in Kubeflow 1.3)