See what a Service really points at
"Is my Service actually hitting healthy pods?" Kubius shows a Service's selector, the pods it matches, how many are ready, its ports and type - so a Service pointing at nothing is immediately obvious.
Works with Google GKE, Amazon EKS, Azure AKS, DigitalOcean, self-managed & more · macOS Sonoma (14) or later
Services, backends and all
Selector to pods
See the Service's selector resolved to the actual pods behind it, so an empty or wrong selector is caught at a glance.
Endpoint health
Related pods are tinted by health - green, amber, red - based on how many matched pods are Running, so a Service backed by failing pods stands out.
Ports and targetPorts
Every port, its protocol and the targetPort it maps to are laid out, so a port mismatch is easy to spot.
Type and routing
ClusterIP, NodePort, LoadBalancer or ExternalName - the type, cluster IP and any external IP/hostname are shown clearly.
In the dependency graph
See the Service in context - what routes to it (Ingress) and what it routes to (pods) - and click through.
Find it fast
Filter Services across namespaces or jump to one with the command palette.
Simple, one-time pricing
Pay once. No subscription.
One-time licence from €49 - no subscription. 14-day free trial, no card required.
Free 14-day trial · macOS Sonoma (14) or later · No agents, nothing to install in-cluster
Questions, answered
How do I tell if a Service is hitting healthy pods?
Kubius resolves the Service's selector to the matching pods and tints them by health, so you can immediately see whether the pods behind the Service are Running - or whether the selector matches nothing.
Can I check for a port mismatch?
Yes - each port and its targetPort are shown side by side, which is where Service misconfigurations often hide.
Does it show LoadBalancer external IPs?
Yes. The Service type, cluster IP and any external IP or hostname are displayed for ClusterIP, NodePort, LoadBalancer and ExternalName services.
Do I need anything in the cluster?
No - Kubius reads Services and their endpoints from the Kubernetes API with your kubeconfig.