Service Status
Last updated
Was this helpful?
1.2
Last updated
Was this helpful?
Services shown in the Down state indicate that there are 0 service instances announcing into the mesh. This would be seen anytime the service is no longer deployed (scaled to 0) but has not been removed from . Additionally, this can be seen if the catalog entry doesn't properly match the announced service information.
The warning state indicates that a service has been under or over provisioned within the mesh. The acceptable provisioned range is set with the minInstances and maxInstances field of the
Make sure the clusterName field on the matches the on the cluster object.
Check the environment variable. Catalog uses this request cluster to discover instances of services running in the mesh, so if the request cluster doesn't know about the target cluster you're troubleshooting, Catalog won't see any instances of it either. You can test this by curling the endpoint of the request cluster's admin server. If you don't see the target cluster listed with an IP address, make sure that routing between the request cluster and the target cluster is correct.
