Service
A Kubernetes Service is an API resource that provides stable network access and service discovery for a changing set of Pods or other specified destinations.
Kubernetes in Action, Second Edition
A Service is a Kubernetes resource that provides a stable network endpoint for a set of application pods or manually specified destinations.
- How it is used
- Provides stable access and connection distribution for changing pod replicas, both between applications and from external clients.
- How deep it goes
- Works through creation, selectors, ports, discovery, exposure types, endpoints and readiness, without detailing the network implementation.
- Examples
- Uses quote and quiz application Services, a ClusterIP YAML manifest, kubectl commands and repeated curl requests.
- What you can do after
- Operate/configure it with kubectl and YAML to expose pods, inspect access addresses and choose internal or external access.
Read how Kubernetes in Action, Second Edition explains service →
Road to Kubernetes
A Kubernetes Service is a Kubernetes API resource that provides a stable network endpoint and routes traffic to a set of Pods.
- How it is used
- Exposes selected Pods for internal communication or internet traffic alongside Deployments.
- How deep it goes
- Works through Service types, selectors, port mappings, cluster DNS, and managed load balancing; leaves HTTPS certificate configuration outside scope.
- Examples
- Uses an NGINX NodePort, PostgreSQL client-to-database communication, and a Python application exposed through a LoadBalancer.
- What you can do after
- Operate/configure it with Kubernetes manifests to expose selected Pods and choose internal or external traffic routing.
Acing the Certified Kubernetes Administrator Exam, Second Edition
A Kubernetes Service is a resource that provides stable network access to a set of Pods and distributes traffic among them.
- How it is used
- Provides a consistent, load-balanced destination for application Pods as they move, restart, or scale.
- How deep it goes
- Works through Service types, selectors, ports, endpoints, DNS access, and troubleshooting with kubectl and YAML.
- Examples
- Uses an nginx Deployment, a cross-namespace curl test, and a misconfigured Service-port repair.
- What you can do after
- Operate/configure it with kubectl and YAML, then diagnose failed access by checking ports, selectors, endpoints, and DNS names.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains service →
Kubernetes for Developers
A Kubernetes Service is a stable networking abstraction that provides connectivity to a group of Pods.
- How it is used
- Provides a stable access point for application Pods, serving internal callers or exposing the application externally.
- How deep it goes
- Works through Service configuration and request routing, including selectors, ports, virtual IPs, and node networking.
- Examples
- Uses a Service YAML file, kubectl commands, an HTTP request, and an internal request routed to a Pod.
- What you can do after
- Operate/configure it with YAML and kubectl to expose a Deployment or give cluster applications an internal endpoint.
Google Anthos in Action
A Kubernetes Service is a resource that provides a stable network endpoint for accessing workloads within a cluster.
- How it is used
- Provides a stable name for reaching application Pods despite changes to Pod IP addresses.
- How deep it goes
- Explains DNS naming, endpoint routing and network-scope options, then demonstrates exposure and port forwarding without detailing Service internals.
- Examples
- Uses namespaced Service DNS names and a minikube Deployment exposed through NodePort and accessed by local port forwarding.
- What you can do after
- Operate/configure it with kubectl to expose a Deployment, verify its Service and forward it to a local port.
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
A Kubernetes abstraction that exposes a set of pods through a stable network endpoint and service-discovery identity.
- How it is used
- Exposes a pod-hosted microservice through DNS within a Kubernetes cluster and, when configured, to external HTTP requests.
- How deep it goes
- Works through YAML selectors, ports, deployment checks, and cleanup; defers detailed scaling and redundancy.
- Examples
- Uses a video-streaming microservice, an Azure LoadBalancer manifest, and kubectl output showing a local NodePort on port 30000.
- What you can do after
- Operate/configure it with YAML and kubectl to deploy, inspect, and remove a microservice’s service.
Platform Engineering on Kubernetes
A Kubernetes Service is a stable network endpoint that exposes a set of Kubernetes workload instances to other clients inside a cluster.
- How it is used
- Provides internal communication and load-balanced access to replicated application containers in a Kubernetes cluster.
- How deep it goes
- Explains names, selectors, ports, ClusterIP routing, and endpoints, while deferring detailed resource management.
- Examples
- Uses frontend, PostgreSQL, Redis, and Kafka Services alongside kubectl listing and description commands.
- What you can do after
- Operate/configure Services with kubectl and connect workloads through stable names, selectors, ports, and generated infrastructure endpoints.
Read how Platform Engineering on Kubernetes explains service →
Machine Learning Platform Engineering
A Kubernetes service is an abstraction that provides stable network access to a changing set of pods.
- How it is used
- Exposes applications to users and enables communication between applications inside a Kubernetes cluster.
- How deep it goes
- Explains pod decoupling, three Service types, port mappings, selectors, manifests, commands, and access tests.
- Examples
- Uses FastAPI joke endpoints, NodePort and ClusterIP manifests, curl checks, and a BentoML inference deployment.
- What you can do after
- Operate/configure Kubernetes Services with manifests, kubectl, selectors, port mappings, and client connectivity checks.
Read how Machine Learning Platform Engineering explains service →
Quarkus in Action
A Kubernetes Service is an API resource that provides stable network access to a set of Kubernetes workloads.
- How it is used
- Provides stable service discovery and network access for workloads whose pods can be created, destroyed, or relocated.
- How deep it goes
- Defines grouping, name-based access, optional load balancing, ports, and generated manifests without covering cluster setup or selector internals.
- Examples
- Uses an Inventory service manifest exposing HTTP and gRPC ports, then applies it with kubectl and tests through port-forwarding.
- What you can do after
- Apply generated Kubernetes manifests and connect to deployed workloads through stable Service names and ports.
Learn Docker in a Month of Lunches, Second Edition
A Kubernetes Service is a network abstraction that exposes selected Pods and routes traffic to them.
- How it is used
- Exposes application traffic and routes it from cluster nodes to selected Pods.
- How deep it goes
- Explains selectors, zero-to-many Pod matches, port mapping, and load balancing without detailing networking internals.
- Examples
- Uses a labeled numbers API Pod, a Service manifest, kubectl inspection, and a curl request to verify routing.
- What you can do after
- Operate/configure a Service with kubectl, select Pods by labels, and verify routed HTTP traffic.
Read how Learn Docker in a Month of Lunches, Second Edition explains service →
gRPC Microservices in Go
A Kubernetes Service is an API resource that provides a stable network endpoint and routes traffic to selected backend Pods.
- How it is used
- Exposes selected Pods as an endpoint for internal clients or public users in a Kubernetes microservice deployment.
- How deep it goes
- Works through Service types, selectors, and port mapping with a YAML manifest; does not detail Kubernetes networking internals.
- Examples
- Uses Shipping for internal access, Payment for a LoadBalancer manifest, and two deployment versions for a canary rollout.
- What you can do after
- Operate/configure it by selecting a Service type and defining selectors and ports for the intended clients and Pods.
Designing Deep Learning Systems: A guide for software engineers
A Kubernetes API resource that provides a stable network endpoint for accessing a set of pods.
- How it is used
- Provides stable master-process discovery for Kubernetes-based distributed training.
- How deep it goes
- Explains service creation, DNS addressing, environment variables, and observed Kubernetes resources, but not service selector details.
- Examples
- Uses a three-pod intent-classification run, a ClusterIP master service, kubectl output, and a service-creation code listing.
- What you can do after
- Configure distributed training to locate its master process through a Kubernetes service DNS name.
Read how Designing Deep Learning Systems: A guide for software engineers explains service →
Related concepts
- ingress objectused by · A Kubernetes Ingress is an API resource that specifies rules for routing external HTTP and HTTPS requests to services within a cluster.
- load balancingimplements · Load balancing is the distribution of requests or computational work across multiple resources to manage demand, reduce workload imbalance, and improve utilization or availability.
- poduses · A Kubernetes Pod is the smallest deployable unit in Kubernetes, grouping one or more co-located containers that share networking and other resources.
- node portincludes · NodePort is a Kubernetes Service type that exposes a service through a designated port on every cluster node and routes traffic to its endpoints.
- label selectoruses · A label selector is a Kubernetes expression that identifies or filters resources whose labels match specified keys, values, or conditions.
- clusterip service typeincludes · ClusterIP is a Kubernetes Service type that exposes selected Pods through a stable virtual IP address accessible only within the cluster.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.