Services and Ingress · Knowledge & Memory Center

Service types

Type	Reachable from	Use
ClusterIP (default)	Inside the cluster	Service-to-service calls
NodePort	`<nodeIP>:30000-32767`	Quick external test, bare metal
LoadBalancer	Cloud load balancer IP	One external IP per service
Headless (`clusterIP: None`)	DNS returns pod IPs	StatefulSets, direct pod addressing
ExternalName	DNS CNAME	Alias an external host

DNS name: <service>.<namespace>.svc.cluster.local

Ingress

One entry point, many hosts and paths, TLS termination.

ingress.yaml

YAML

1apiVersion: networking.k8s.io/v1

2kind: Ingress

3metadata:

4 name: web

5spec:

6 ingressClassName: nginx

7 tls:

8 - hosts: [app.example.com]

9 secretName: web-tls

10 rules:

11 - host: app.example.com

12 http:

13 paths:

14 - path: /

15 pathType: Prefix

16 backend:

17 service:

18 name: web

19 port: { number: 80 }

Check the wiring

Debug connectivity

SHELL

1kubectl get svc,endpoints web

2kubectl get ingress

3kubectl describe ingress web

4kubectl run tmp --rm -it --image=busybox -- wget -qO- http://web

!

An Ingress does nothing without an ingress controller (ingress-nginx, Traefik or a cloud controller). Empty endpoints mean the Service selector matches no ready pods.