<p><strong><em>How to configure the health check for the service that is automatically registered using the Consul sync Catalog.?</em></strong></p>

Ankit Singh
<p>The health checks Kubernetes performs are called <a href="https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/" rel="nofollow noreferrer">"probes"</a>. There are three types of probes - liveness, readiness, and startup - and they are checks on the <em>application/process</em> running in a Container, not the <a href="https://kubernetes.io/docs/concepts/services-networking/service/" rel="nofollow noreferrer">Kubernetes Service(s)</a> in front of the application's Pods. (One Pod can have one or more Containers; usually, as a best practice, a single application/process runs in a given Container)</p>

<p>Automatically syncing Kubernetes Services to Consul has no bearing on the probes executed against Containers running in Pods on the same Kubernetes cluster.</p>

<p>Kubernetes wouldn't check the health of Consul services synced to Kubernetes.</p>

<p>The answer to the question</p>

<blockquote>
  <p>How to configure the health check for the service that is
  automatically registered using the Consul sync Catalog.?</p>
</blockquote>

<p>is "It is not possible to configure Kubernetes probes for the Kubernetes Services synced with Consul or for Consul Services synced with Kubernetes. Kubernetes probes are configured for the application/process running in Container that is in a Kubernetes Pod".</p>
