Understand Kubernetes networking: ClusterIP, NodePort, LoadBalancer, Ingress, and policy.

On this page

Kubernetes Networking: Services, Ingress, and Network Policies

Kubernetes networking can be confusing. Here’s a concise guide to services, ingress, and network policy.

Services #

ClusterIP: Internal cluster DNS; default for in-cluster traffic.
NodePort: Expose a port on every node; good for dev or legacy.
LoadBalancer: Cloud LB per service; use when you need a dedicated external IP.

Ingress #

Ingress = HTTP(S) routing (host/path) to backend services. You need an Ingress controller (e.g. nginx, AWS ALB).
TLS: Terminate at ingress; use cert-manager for certificates.

yaml.yaml

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: myapp
spec:
  ingressClassName: nginx
  rules:
    - host: myapp.example.com
      http:
        paths:
          - path: /
            pathType: Prefix
            backend:
              service:
                name: myapp
                port: { number: 80 }

Network Policies #

NetworkPolicy restricts pod-to-pod and pod-to-external traffic. Default-deny and allow only what’s needed.
Start with a policy that allows DNS and ingress; then add app-specific rules.

Best practice: document your ingress and network policy approach so every new service follows the same pattern.

Kubernetes Networking: Services, Ingress, and Network Policies

Kubernetes Networking: Services, Ingress, and Network Policies

Services #

Ingress #

Network Policies #

Stay Updated

Operational Checklist: Secure Container Supply Chain Controls

A Pragmatic Multi-Region Strategy for Small Teams

More from DevOps

Incident Postmortems That Actually Prevent Repeat Failures

How We Cut Our Docker Image Size by 80% and Why It Matters

Artifact Promotion Instead of Rebuilds: The Release Control Pattern That Stopped Drift

Incident Postmortems That Actually Prevent Repeat Failures

How We Cut Our Docker Image Size by 80% and Why It Matters

Artifact Promotion Instead of Rebuilds: The Release Control Pattern That Stopped Drift

Blue-Green Deployment Guardrails in Kubernetes: Lessons from a Failed Friday Rollout

Monitoring That Actually Helps On-Call: Alerts, Dashboards, and Runbooks

Secrets Management in Practice: From .env Files to Vault

About Kiril urbonas

Kubernetes Networking: Services, Ingress, and Network Policies

Services#

Ingress#

Network Policies#

Stay Updated

Operational Checklist: Secure Container Supply Chain Controls

A Pragmatic Multi-Region Strategy for Small Teams

More from DevOps

Incident Postmortems That Actually Prevent Repeat Failures

How We Cut Our Docker Image Size by 80% and Why It Matters

Artifact Promotion Instead of Rebuilds: The Release Control Pattern That Stopped Drift

About Kiril urbonas

Services #

Ingress #

Network Policies #