Running into an issue while using Gloo Network for Cilium? 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, Cilium, 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 Network 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.

  2. Review the following sections to help you scan your environment for errors or warnings.


The Cilium and Gloo health card of the dashboard provides a check of the Cilium and Gloo Network installations in your clusters. Each tab provides an at-a-glance status of the health of each Cilium or Gloo Network component. In the Gloo tab, you can click the button beside each component to see its pod logs. The environment check shows the count and state of all versions of Cilium or Gloo Network that are installed in your environment, and 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 Network control plane.

  1. To filter clusters by the cluster’s Gloo Network 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. Click More Details to see a more detailed dashboard for the cluster.

    Figure: Cluster details page


On the Services page, review a list of the discovered services across all clusters in your Gloo setup. Quickly find out if traffic cannot reach your services 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.

Figure: Services page

Note that the health of your services on the Services overview page refers to whether network traffic requests are getting fulfilled by the service. You can review the configuration health of the service by clicking Details.

From the Details page of a service:

  • To debug the service, click View YAML to view the service’s YAML configuration.
  • See an analysis of the service’s error rate and latency in the Service Signals card.
  • View the Graph tab to visualize the network traffic that reaches your service mesh. For more information about how to use the graph, see Graph.
  • If you enable tracing in the Gloo telemetry pipeline, you can see request traces for a service in the built-in Jaeger UI that you can find in the Tracing tab. For more information about how to enable and use the tracing interface, see Tracing.

Figure: Services page


The Resources section provides the configuration of each type of 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: Kubernetes resources page