I'm setting up GKE Gateway API in GKE cluster by following this tutorial and docs.
The Gateway resource is working fine. It has created a Load Balancer resource on GCP and assigned a static IP address to it.
apiVersion: v1
kind: Namespace
metadata:
name: infra-ns
labels:
shared-gateway-access: "true"
---
kind: Gateway
apiVersion: gateway.networking.k8s.io/v1beta1
metadata:
name: external-http
namespace: infra-ns
spec:
gatewayClassName: gke-l7-gxlb
listeners:
- name: http
protocol: HTTP
port: 80
allowedRoutes:
namespaces:
from: Selector
selector:
matchLabels:
shared-gateway-access: "true"
The HTTPRoute resource apparently is working fine. It was recognized by the Gateway.
apiVersion: v1
kind: Namespace
metadata:
name: other-namespace
labels:
shared-gateway-access: "true"
---
apiVersion: v1
kind: Service
metadata:
annotations:
cloud.google.com/neg: '{"ingress": true}'
name: myservice
namespace: other-namespace
spec:
ports:
- name: myservice
port: 80
protocol: TCP
targetPort: 8080
selector:
app: myservice
type: NodePort
---
kind: HTTPRoute
apiVersion: gateway.networking.k8s.io/v1beta1
metadata:
name: myhttproute
namespace: other-namespace
spec:
parentRefs:
- kind: Gateway
name: external-http
namespace: infra-ns
hostnames:
- "demo.example.com"
rules:
- backendRefs:
- name: myservice
port: 80
I can see NEG was created for my service and the load balancer refers to it as a Backend Service. The problem is the Health check showing my service as UNHEALTHY while I have tested the only pod beneath it and it's healthy.
What I see in GCP console is the wrong path for health checks. Manual edit doesn't work since it comes back to the same. And I haven't found anything to configure this path in HTTPRoute. Anyway, I belive it doesn't have to be configured since it should get the health path stated in livenessProbe/readinessProbe which is already present in the manifest of Deployment and it's /health, not /.
Am I doing something wrong? Why the health check path differs from the stated in liveness and readiness probes?
$ kubectl -n other-namespace describe deployment myservice
...
Containers:
myservice:
Image: myserviceimage:latest
Port: 8080/TCP
Host Port: 0/TCP
Requests:
cpu: 1m
memory: 1Mi
Liveness: http-get http://:8080/health delay=10s timeout=5s period=10s #success=1 #failure=3
Readiness: http-get http://:8080/health delay=2s timeout=3s period=2s #success=1 #failure=2
...
