Networking
Inspect Services, Ingresses, Endpoints, and NetworkPolicies across every namespace.
Use the Networking page to inspect how traffic moves through the cluster. Read Services, Ingresses, Endpoints, and NetworkPolicies without jumping back to kubectl.
Services
Use Services to see the stable front door for a workload. The list shows the service type, ClusterIP, and ports.
ClusterIPfor internal traffic inside the cluster.NodePortwhen you need a node-level port for quick access.LoadBalancerwhen the cluster exposes an external load balancer.ExternalNamewhen the Service points to a DNS name instead of a selector.
Services with a selector also show a Forward button that starts a port forward to a ready backing pod.
The detail view shows the full Service spec and YAML.
Ingresses
Use Ingresses to inspect HTTP routing into the cluster. The list shows hosts, paths, and backend Services, while the detail view shows TLS secrets, annotations, and the rules table.
Endpoints
Use Endpoints when you need the raw backend addresses behind a Service. This view is most useful when a Service has no healthy backends.
NetworkPolicies
Use NetworkPolicies to understand which pods can talk to each other.
Phase 1 is view-only for NetworkPolicies. Create and edit them with kubectl apply or by editing the YAML for another resource.