The changes made to readinessProbe are not propagated to Google Cloud Load Balancer.
How to reproduce it (as minimally and precisely as possible):
- Create a deployment with following contents
readinessProbe: httpGet: path: /healthcheck port: 8000
- Create an ingress pointing to the pods created by that deployment. (via a NodePort service)
- Change the path in health check
In the Pod, you still see
GoogleHC/1.0 visiting the old health check end point.
Kubernetes version: 1.14.10-gke.17
Cloud being used: GKE
Host OS: container-os
CNI and version: GKE default (kubenet?)
CRI and version: Docker (default)