Running into an issue while using Gloo Mesh Core? Try the following general debugging steps to find why things might not behave as expected.

Debug your environment

  1. Make sure that you run a supported version of Gloo, Istio, and Kubernetes and their related command line interface (CLI) tools. If not, upgrade your version and CLIs.
  2. Review your infrastructure provider for any errors, incidents, or outages that might impact your clusters, load balancers, and related infrastructure. Common configuration problems happen in the following resources:
    • Firewalls
    • Application load balancer (ALB) settings
    • Expired or malformatted certificates, tokens, and secrets
  3. Check your Gloo Mesh Core environment for errors, such as an expired license or an unhealthy pod.
  4. Depending on which component has issues, try one of the debugging guides:

Debug with the UI

The Gloo UI provides a single pane of glass from which you can assess what might be wrong in your environment.

  1. Open the Gloo UI. The Gloo UI is served from the gloo-mesh-ui service on port 8090. You can connect by using the meshctl or kubectl CLIs.

    • meshctl: For more information, see the CLI documentation.
        meshctl dashboard
    • kubectl:
      1. Port-forward the gloo-mesh-ui service on 8090.
          kubectl port-forward -n gloo-mesh svc/gloo-mesh-ui 8090:8090
      2. Open your browser and connect to http://localhost:8090.
  2. Review the following sections to help you scan your environment for errors or warnings.


The Gloo and Istio health card of the dashboard provides a check of the Gloo Mesh Core and Istio installations in your clusters. Each tab provides an at-a-glance status of the health of each Gloo Mesh Core and Istio component. You can click the link button beside each component to see more details about its health. The environment check shows all versions of Gloo Mesh Core or Istio that are installed in your environment, the state of each installation, and the number of clusters in your environment. The environment checks can help you identify overall issues with your installations, such as version mismatches between the control and data planes.


The Inventory section provides an at-a-glance look at the health of registered clusters and discovered services that make up your Gloo environment.


On the Clusters page, review basic details of each cluster that you registered with the Gloo Mesh Core control plane.

  1. To filter clusters by the cluster’s Gloo Mesh Core installation health, click the Healthy and Unhealthy buttons. You can also use the Sort by Name dropdown or the search bar to filter clusters by name.

    Figure: Clusters page
  2. Expand each cluster card to review further information about the number of namespaces, services, gateways, and nodes in the cluster. Additionally, you can click More Details to see a more detailed dahboard for the cluster. This dashboard can help you find errors in your Gloo setup, such as a missing CRD in the following example figure.

    Figure: Cluster details page


On the Services page, review a list of the discovered services across all clusters in your Gloo setup. You can quickly find services that are unhealthy by clicking the Healthy and Unhealthy buttons. You can also filter services by name using the search bar, filter by in-mesh and out-of-mesh services, and modify the timeframe that services are available in by using the dropdown menu.

To debug specific services, click View YAML to view the service’s YAML configuration.

Figure: Services page


The Resources section provides the configuration of each Istio, Cilium, Gateway API, and Kubernetes resource in your environment to help you locate and resolve configuration issues. With the Filter by… dropdown, you can filter services by resource type.

To debug specific resources, click View YAML to view the resource’s YAML configuration.

Figure: Istio resources page