We Ranned the Kubecost in the cluster and we got a the new issue while using of virtual service

0

The Kubecost cost-analyzer service is properly configured and exposing port 9003 for the cost-model container. The service is targeting the correct port (9003) and has an endpoint pointing to the cost-model container's IP (10.164.100.70:9003). When you executed the curl command inside the cost-analyzer-frontend container to access the healthz endpoint of the cost-model container (http://localhost:9003/healthz), it returned an empty response. This indicates that the cost-model container is running and responding to the healthz endpoint, but the response is empty.

livenessProbe: httpGet: path: /healthz port: 9003

readliness: httpGet: path: /healthz port: 9003

additionally with the intial deploy seconds and other attributes too

Venkata
已提问 24 天前76 查看次数
没有答案

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则

相关内容