This example demonstrates HTTP sticky sessions in Kubernetes, where client requests are consistently routed to the same backend pod. It shows the configuration for a frontend HAProxy service load balancer that inserts a `SERVERID` cookie into responses, and a backend service with five replica pods serving hostnames. The code uses Kubernetes YAML manifests for the service and replication controllers, along with HAProxy’s `cookie SERVERID insert indirect nocache` directive. The included shell commands verify sticky behavior by curling the public endpoint with and without the cookie, and then creating an Ingress with TLS.