Exam Professional Cloud Developer topic 1 question 12 discussion

B: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

Option B is the correct code snippet to include in the Pod configuration in order to use the /healthz endpoint as a readiness probe. The liveness probe, specified in option A, is used to determine whether the application is running and responsive. If the liveness probe fails, the application is considered to be in a failed state and will be restarted. The readiness probe, specified in option B, is used to determine when a Pod is ready to receive traffic. If the readiness probe fails, the Pod will not receive traffic from the load balancer until it becomes healthy again. Option C, loadbalancerHealthCheck, is not a valid field in a Pod configuration. Option D, healthCheck, is also not a valid field in a Pod configuration.

Readiness probe marks the pod as "Running" and can START accepting traffic. However, after the pod is in a "Running" state, the Liveness probe comes in and acts as the health check for the entire lifecycle of the pod. So think of it this way. The pod passes its initial check (readiness), accepts traffic for a while then crashes (logically, the pod can still be "Running"). The Liveness probe is responsible for detecting it. Otherwise, the LB could still pass traffic to a pod that can't serve traffic. Therefore, I believe it's A.

B is correct

B is correct according with https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

https://cloud.google.com/kubernetes-engine/docs/how-to/ingress-features ingress backendconfig can set healthCheck, but this resource can not set httpGet ``` apiVersion: cloud.google.com/v1 kind: BackendConfig metadata: name: my-backendconfig spec: healthCheck: checkIntervalSec: INTERVAL timeoutSec: TIMEOUT healthyThreshold: HEALTH_THRESHOLD unhealthyThreshold: UNHEALTHY_THRESHOLD type: PROTOCOL requestPath: PATH port: PORT ```

B is correct

https://cloud.google.com/kubernetes-engine/docs/concepts/ingress: "GKE can infer some or all of the parameters for a health check if the Serving Pods use a Pod template with a container whose readiness probe has attributes that can be interpreted as health check parameters. See Parameters from a readiness probe for implementation details and Default and inferred parameters for a list of attributes that can be used to create health check parameters. Only the GKE Ingress controller supports inferring parameters from a readiness probe." B is correct

B is correct answer https://cloud.google.com/blog/products/gcp/kubernetes-best-practices-setting-up-health-checks-with-readiness-and-liveness-probes