<p>I have a web server on port 8080. I have a Ingress object made by Google routing external traffic to a service that points to the pod.</p>

<p>My logs are littered with a request from 10.4.0.1:(some rotating large port) at "/" and it is eating CPU cycles as my web server generates the HTML to respond. It seems like a health check probe.</p>

<p>My pod has the following probe configs on my deployment:</p>

<pre><code>        readinessProbe:
          httpGet:
            path: "/status"
            port: 8080
          initialDelaySeconds: 10
        livenessProbe:
          httpGet:
            path: "/status"
            port: 8080
          initialDelaySeconds: 
</code></pre>

<p>Though it looks like I may have missed something in the configuration.</p>

<p>I've used <code>tcpdump -X port 8080</code> to examine the traffic. It looks as though the same source (10.4.0.1) are conducting the status check (at "/status") and a mysterious check at root ("/") back to back. It seems as though it is the kubelet but I haven't found proof. The pod IP range is <code>10.4.0.0/14</code>. It also seems as though the new configuration worked but the default probe config wasn't removed.</p>

<p>After applying changes to the deployment, do I need to purge and restart the service? Ingress? Node? I'm new to Kubernetes and am lost.</p>

<p>Help of any kind is greatly appreciated!</p>

jator0
<p>To resolve the issue I had to change the configuration on a VM Instance Health Check that is part of Google's Compute Engine API. Setting the path to "/status" seemed to do the trick. So in short there is a health check from both kubernetes and GCE.</p>
