Skip to main content
The Networking section provides visibility into how traffic flows to and within your Kubernetes cluster.

​
Overview

Kubernetes networking resources control how applications communicate:
  • Services - Stable endpoints for accessing pods
  • Ingresses - HTTP/HTTPS routing from outside the cluster
  • Ingress Classes - Configure which ingress controller handles routes
  • Endpoints - Backend targets for services
  • Network Policies - Firewall rules between pods

​
Accessing Networking Resources

Navigate to your cluster and click Kubernetes in the sidebar. Networking resources include:

​
Services

Services provide stable network identities for pods.

​
Service Types

​
Viewing Services

The Services list shows:

​
Service Details

Click a service to view:
  • Selector - Labels used to find backend pods
  • Ports - Port configurations
  • Endpoints - Current backend pod IPs
  • Session Affinity - Sticky session configuration
  • Events - Recent service events

​
Ingresses

Ingresses expose HTTP/HTTPS routes from outside the cluster.

​
Viewing Ingresses

​
Ingress Details

Click an ingress to view:
  • Rules - Host and path routing rules
  • TLS - Certificate configuration
  • Backend - Default backend service
  • Annotations - Controller-specific settings
  • Status - Load balancer addresses

​
Ingress Rules

Each rule defines routing:

​
Ingress Classes

Ingress Classes determine which controller handles an Ingress.

​
Viewing Ingress Classes

Common controllers:
  • nginx - NGINX Ingress Controller
  • traefik - Traefik
  • alb - AWS ALB Ingress Controller
  • gce - Google Cloud Load Balancer

​
Endpoints

Endpoints are the actual pod IPs backing a Service.

​
Viewing Endpoints

​
Endpoint Details

  • Subsets - Groups of ready and not-ready addresses
  • Ports - Port configurations
  • Addresses - Pod IPs and node information

​
Troubleshooting with Endpoints

If a Service isn’t routing traffic:
  1. Check if Endpoints exist for the Service
  2. Verify pod IPs appear in the Endpoints
  3. If empty, check the Service’s selector matches pod labels
  4. Verify pods are in Running state

​
Network Policies

Network Policies are firewall rules for pod-to-pod traffic.

​
Viewing Network Policies

​
Network Policy Details

  • Pod Selector - Labels that select target pods
  • Ingress Rules - Allowed incoming traffic sources
  • Egress Rules - Allowed outgoing traffic destinations
  • Policy Types - Whether ingress/egress are enforced

​
Policy Example

​
Common Tasks

​
Troubleshooting Service Connectivity

  1. Navigate to Services and find the service
  2. Click to view details
  3. Check Endpoints:
    • If empty: Verify pod selectors and pod labels match
    • If present: Verify pods are running and healthy
  4. Check Events for errors

​
Checking Ingress Configuration

  1. Navigate to Ingresses
  2. Click the ingress to view rules
  3. Verify:
    • Host matches your domain
    • Paths route to correct services
    • TLS is configured if using HTTPS
  4. Check the Address for the external endpoint

​
Debugging Network Policies

  1. Navigate to Network Policies
  2. Find policies in the affected namespace
  3. Check if policies are blocking expected traffic
  4. Verify pod selectors and allowed sources/destinations

​
Tips

Check Endpoints First: Empty Endpoints usually mean a selector mismatch between Service and Pods.
Ingress Annotations: Most ingress functionality is configured via annotations specific to your controller.
Default Deny: If using Network Policies, start with a default-deny policy and explicitly allow required traffic.
Still have questions? Join our Slack community and we’ll help out.