Kubernetes - Health Checks and ProbesWhy does Kubernetes use TCP probes instead of HTTP probes in some cases?ABecause TCP probes are faster than HTTP probesBBecause some applications only accept TCP connections without HTTP protocolCBecause HTTP probes require extra configuration for portsDBecause TCP probes can check disk usageCheck Answer
Step-by-Step SolutionSolution:Step 1: Understand probe protocol differencesHTTP probes require the application to respond to HTTP requests, TCP probes only check if port is open.Step 2: Identify use case for TCP probesSome apps do not speak HTTP but accept TCP connections, so TCP probes are used.Final Answer:Because some applications only accept TCP connections without HTTP protocol -> Option BQuick Check:TCP probes used for non-HTTP apps = Because some applications only accept TCP connections without HTTP protocol [OK]Quick Trick: Use TCP probes for apps without HTTP protocol [OK]Common Mistakes:Assuming TCP probes are always fasterThinking TCP probes check disk or CPUConfusing HTTP probe configuration complexity
Master "Health Checks and Probes" in Kubernetes9 interactive learning modes - each teaches the same concept differentlyLearnWhyDeepVisualTryChallengeProjectRecallTime
More Kubernetes Quizzes Ingress - Why Ingress manages external access - Quiz 7medium Ingress - Path-based routing - Quiz 2easy Networking - Service mesh concept overview - Quiz 12easy Networking - Why Kubernetes networking matters - Quiz 14medium Resource Management - Cluster Autoscaler concept - Quiz 13medium Resource Management - Vertical Pod Autoscaler concept - Quiz 4medium Resource Management - CPU requests and limits - Quiz 15hard Resource Management - Horizontal Pod Autoscaler - Quiz 14medium Scheduling - DaemonSets for per-node workloads - Quiz 12easy Secrets - Using Secrets as mounted volumes - Quiz 7medium