Ingress

A flat table of every Ingress the agent has synced.

Column	What it shows
Namespace
Name
Class	The ingressClassName — Traefik, nginx, ALB, and so on.
Rules	Host and path rules, and the backend Service each routes to.
Age	Time since creation.

An Ingress with no class is worth a second look: which controller picks it up then depends on the cluster’s default IngressClass, and that is a common cause of a route that silently never serves.

Traefik runtime

For Traefik, Runtimez can also read what the controller actually built and served — its own status for every router and request counts by status code — and use them in root-cause analysis. It takes a few settings on the agent and on Traefik; see Traefik runtime.

From the CLI

rtz get ing -n payments