Ingress object
A Kubernetes Ingress is an API resource that specifies rules for routing external HTTP and HTTPS requests to services within a cluster.
Kubernetes in Action, Second Edition
The Ingress API is the Kubernetes API for declaring external HTTP and HTTPS access to services through ingress resources.
- How it is used
- Exposes multiple cluster Services to external HTTP or HTTPS clients through host- and path-based routing at a shared entrypoint.
- How deep it goes
- Works through manifests, matching rules, controller behavior, inspection, TLS, and controller selection; leaves custom HTTPRoute contents unexplored.
- Examples
- Uses single- and multi-host YAML manifests, exact and prefix path routing, kubectl inspection, and curl --resolve tests.
- What you can do after
- Operate/configure it with a manifest to expose Services, inspect the public address, test routing, and add TLS or an IngressClass.
Read how Kubernetes in Action, Second Edition explains ingress object →
Kubernetes for Developers
Ingress is a Kubernetes API resource that routes external HTTP or HTTPS traffic to Services and can terminate or re-encrypt TLS connections.
- How it is used
- Routes external HTTP requests to multiple Services through one address, with optional HTTPS handling and request-based autoscaling.
- How deep it goes
- Works through path and host rules, deployment checks, and TLS Secret configuration; does not detail load-balancer internals.
- Examples
- Uses YAML for path-based and host-based routing, a TLS-enabled Ingress, and kubectl output showing an assigned address.
- What you can do after
- Operate/configure it to publish multiple Services on one external IP and add HTTPS with a TLS Secret.
Read how Kubernetes for Developers explains ingress object →
Acing the Certified Kubernetes Administrator Exam, Second Edition
An Ingress is a Kubernetes API object that defines external HTTP or HTTPS routing rules to backend services.
- How it is used
- Routes external HTTP or HTTPS requests by host or path to internal Services.
- How deep it goes
- Works through controller installation, backend creation, an Ingress manifest and verification, without detailing controller internals or TLS configuration.
- Examples
- Uses a hello Deployment, a ClusterIP Service, host-based Ingress rules, `kubectl` status checks and a `curl` response.
- What you can do after
- Operate/configure it by creating an ingress controller and routing a named host to a Service, then verifying the response.
Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains ingress object →
Platform Engineering on Kubernetes
A Kubernetes Ingress is a resource that defines routing for traffic entering a cluster from external clients toward internal services.
- How it is used
- Routes external client traffic through a controlled entry point to services inside a Kubernetes cluster.
- How deep it goes
- Explains service-name and path-based routing, inspection commands, and controller requirements, but defers detailed resource management.
- Examples
- Uses a frontend backend, the root path, nginx, localhost, and kubectl get and describe commands.
- What you can do after
- Operate/configure Ingress resources with kubectl and route external paths to named Kubernetes services.
Read how Platform Engineering on Kubernetes explains ingress object →
Learn Docker in a Month of Lunches, Second Edition
Ingress is the network routing layer that controls how external or internal traffic reaches an application service.
- How it is used
- Controls whether Azure Container Apps expose services publicly or route them internally between containers.
- How deep it goes
- Explains internal access, TCP transport, exposed ports, target ports, and revision rollout through Azure CLI commands.
- Examples
- Uses a PostgreSQL database route configured internally over TCP on port 5432.
- What you can do after
- Operate/configure Azure Container Apps ingress with Azure CLI for private service communication.
Read how Learn Docker in a Month of Lunches, Second Edition explains ingress object →
gRPC Microservices in Go
An Ingress is a Kubernetes API resource that defines rules for routing external HTTP and HTTPS traffic to services in a cluster.
- How it is used
- Routes external microservice requests by path to Kubernetes Services through an Ingress controller.
- How deep it goes
- Works through an Order Ingress manifest, controller installation, and NGINX configuration refresh, without detailing controller internals.
- Examples
- Uses an /Order route to the order Service, an ingress.local TLS host, and a local gRPC request with grpcurl.
- What you can do after
- Operate/configure it with an NGINX Ingress controller to route a gRPC service through a shared load balancer.
Server-Side WebAssembly
An Ingress is a Kubernetes API resource that defines routing of external HTTP traffic to services based on hostnames or paths.
- How it is used
- Routes external HTTP traffic into Kubernetes services, providing a stable endpoint for deployed applications.
- How deep it goes
- Defines a complete path-prefix manifest and contrasts it with port forwarding, but does not detail controller internals.
- Examples
- Uses the scaling-spin service, the / path prefix, port 80, and a kubectl-applied Ingress manifest.
- What you can do after
- Operate/configure an Ingress manifest that forwards HTTP paths to a Kubernetes service.
Google Anthos in Action
Ingress is a Kubernetes API resource that defines rules for routing external HTTP and HTTPS traffic to services.
- How it is used
- Routes external web traffic to Kubernetes services and exposes applications through Anthos deployments.
- How deep it goes
- Defines the routing role and Anthos deployment limitation but does not provide manifest syntax or controller internals.
- Examples
- Uses the Anthos Features menu and Traffic Director as operational examples.
- What you can do after
- Operate/configure Ingress through the Google Cloud console, gcloud, or fleet management API.
Related concepts
- serviceuses · 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.
- ingress routing rulehas part · An ingress routing rule maps conditions such as a host and path to a destination service and port for incoming network traffic.
- ingress controllerimplemented by · An ingress controller is a Kubernetes component that implements Ingress routing rules by directing external network traffic to services within a cluster.
- load balancingconfigures · Load balancing is the distribution of requests or computational work across multiple resources to manage demand, reduce workload imbalance, and improve utilization or availability.
- gateway apialternative to · The Kubernetes Gateway API is a networking standard for defining gateways, listeners, and traffic routing between external clients and cluster services.
- HTTPuses · HTTP is a standardized application-layer protocol that defines request-and-response messages for transferring resource representations between networked systems.
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.