K8 Gateway Api Crd

Must Learn - Kubernetes Gateway API | This will replace Ingress in Future

drawback 1 :-ingress supported alb annotations varies from controller to controller

drawback 2 :-updating same ingress file.

gateway api is solving the problem.

gateway resource, http route resource—CRD

commands :- kind create cluster , helm install eg oci://docker.io/envoyproxy/gateway-helm --version v1.6.1 -n envoy-gateway-system --create-namespace, kubectl get crd -A,kubectl apply -f svc-account.yaml,kubectl apply deploy.yaml,kubectl -f apply svc.yaml,apply gateway_class.yaml,apply httproute.yaml

docker ps,docker exec -it containerid /bin/bash, curl cluster ip to check service working or not

kubectl get pods -n envoy-gateway-system

Summary: Ports 80/443 handle application traffic; 8081/8443 are for Envoy management. The service exposes these ports so external traffic (via LoadBalancer/NodePort) can reach the Envoy proxy pods, which then route to your backend services based on HTTPRoute configurations.

kubectl port-forward svc/envoy-default-eg-e41e7b31 9090:80 -n envoy-gateway-system

curl -- header "Host: www.example.con" http://localhost:9090/get

**Flow:** 1. Client → `10.0.0.100:80` (Gateway Service External IP) 2. Gateway Service → `10.244.1.5:80` (Envoy Pod) 3. Envoy Pod → `10.96.7.15:3000` (Backend Service) 4. Backend Service → `10.244.2.10:3000` (Backend Pod) 5. Backend Pod processes request and returns response 6. Response flows back through the same path in reverse