Istio health check improvement
- Removing default service as single point of failure - @lucynliu we discussed this some time ago, we can take advantage of istio
directResponsefeature, which it is being made by the istio-gateway pod. - Using istio gw feature directResponse
- Istio Gw it is more reliable as health check
- Got rid of default service
On Issue osdu/platform/domain-data-mgmt-services/rock-and-fluid-sample/rafs-ddms-services#135 (closed) we are noticing the 502 Bad Gateway I had changed this value to use the direct health check from the istio gateway instead when doing our aggressive integration tests, looks like default service can get stuck in a random conditions. The istio change presented in this MR improved our integration tests a lot.
I plan to open another MR for AppGw to use /healthz instead of / as health check, however this is needed first to avoid service disruption.
I'll still be pending to the Istio version upgrade, would suggest to use the 1.18.x, will include that in different MR.
Related to #25
Edited by Arturo Hernandez [EPAM]