Context A pod is running on the cluster but it is not responding. Task The desir . . .

Panidhar T:
Context A pod is running on the cluster but it is not responding. Task The desired behavior is to have Kubemetes restart the pod when an endpoint returns an HTTP 500 on the /healthz endpoint. The service, probe-pod, should never send traffic to the pod while it is failing. Please complete the following: • The application has an endpoint, /started, that will indicate if it can accept traffic by returning an HTTP 200. If the endpoint returns an HTTP 500, the application has not yet finished initialization. • The application has another endpoint /healthz that will indicate if the application is still working as expected by returning an HTTP 200. If the endpoint returns an HTTP 500 the application is no longer responsive. • Configure the probe-pod pod provided to use these endpoints • The probes should use port 8080

Mumshad Mannambeth:
This is to configure a health check on a POD. Looks straight forward. Can you explain what area you are having trouble with? Can you please go through the video about health checks and make attempt to create the health check configuration based on the above requirements and post below? We can then help verify it.

Panidhar T:
Thanks for reply if we use below sample pod from http://kubernetes.io|kubernetes.io wiki

Panidhar T:

apiVersion: v1
kind: Pod
metadata:
  labels:
    test: liveness
  name: liveness-http
spec:
  containers:
  - name: liveness
    image: <http://k8s.gcr.io/liveness|k8s.gcr.io/liveness>
    args:
    - /server
    livenessProbe:
      httpGet:
        path: /healthz
        port: 8080
        httpHeaders:
        - name: Custom-Header
          value: Awesome
      initialDelaySeconds: 3
      periodSeconds: 3

Panidhar T:
is it more than enough ? @Mumshad Mannambeth