snellius

Observability UI for kgateway

See the whole picture.

Your whole kgateway setup, in one view. See what's healthy, why a route won't attach, and what each Gateway manages. Read-only, one Helm chart.

Get startedView on GitHub
The Snellius overview for a kgateway install: two problems that need attention, healthy processes, and counts of what it manages

How it works

One picture, four sources

White light looks like one colour, but a prism shows the wavelengths it is made of. The picture Snellius gives you works the same way: one view per install, computed from four sources in your cluster. It reads them through the Kubernetes API and never changes anything.

The picture you see

A health state per install

Problems ranked by severity, each with a stable finding code, the evidence behind it and how to fix it.

  • Resource status

    The conditions kgateway writes on Gateways, routes and policies.

  • Computed attachment

    What Gateway API rules say should attach, checked against that status.

  • Controller metrics

    Config the proxies rejected, and what the controller built for each Gateway.

  • Proxy and pod signals

    Readiness, restarts, Warning Events and proxy stats.

Health overview

Know what's wrong first

Each install gets one health state. Problems are ranked by severity, and each carries a stable finding code, its evidence and how to fix it.

Read the guide
The health overview: one error and one warning, each with a KGWUI finding code, and healthy controller and proxies

Attachment

See why a route is or isn't attached

Snellius works out which listeners should accept a route, and how delegation resolves. It shows that next to the controller's status, and says when the two disagree.

Read the guide
A route's parent card: the controller accepted it, and the computed outcome agrees on both listeners

Explorer

Every Gateway, listener and route

Browse Gateways, ListenerSets and routes. Check listeners, proxies, conditions and what the controller built, and filter routes by status and reason.

Read the guide
A Gateway's listeners: both healthy, with attached route counts that agree with the computed counts

Only get, list and watch

The ClusterRole grants read verbs only. Snellius never changes your cluster.

Never reads Secrets

Secrets, ConfigMaps and the proxy and port-forward subresources stay out of its RBAC.

Private by default

There is no login yet. The chart creates a ClusterIP Service only, and you open the UI with a port-forward. Read the trust model.

Install

Running in two commands

Tested with kgateway 2.3, 2.4 and 2.5. You need Helm, kubectl and a cluster that runs kgateway.

Quick start 
# Install the chart, then open http://localhost:8080
helm install ui oci://ghcr.io/duncandoyle/charts/snellius \
  -n snellius --create-namespacekubectl -n snellius port-forward svc/ui-snellius 8080:80