Say you have a K8S pod that has a readiness probe set up, and at some point that probe fails. The docs say that the pod remains alive but is marked as "Not ready" and "does not receive traffic through Kubernetes Services". When that happens, do requests made directly to the pod's IP address still succeed? What about existing websocket connections to that pod - do they remain connected?
Can K8S pods marked as "Not ready" still receive direct requests?
163 Views Asked by Graeme Perrow At
1
There are 1 best solutions below
Related Questions in KUBERNETES
- Golang == Error: OCI runtime create failed: unable to start container process: exec: "./bin": stat ./bin: no such file or directory: unknown
- I can't create a pod in minikube on windows
- Oracle setting up on k8s cluster using helm charts enterprise edition
- Retrieve the Dockerfile configuration from the Kubernetes and also change container Java parameter?
- Summarize pods not running, by Namespace and Reason - I'm having trouble finding the reason
- How to get Java running parameters from Spring Boot running inside container in pod where no ps exist
- How do we configure prometheus server to scrape metrics from a pod with Istio sidecar proxy?
- In rke kube-proxy pod is not present
- problem with edge server registration in Eureka
- Unable to Access Kubernetes LoadBalancer Service from Local Device Outside Cluster
- Kubernetes cluster on GCE connection refused error
- Based on my experience, I've outlined the Kubernetes request flow. Could someone please add or highlight any points I might have overlooked?
- how to define StackGres helm chart "restapi" values to use internal LoadBalancer - AWS EKS
- Python3.11 can't open file [Errno 2] No such file or directory
- Cannot find remote pod service - SERVICE_UNAVAILABLE
Related Questions in READINESSPROBE
- "Readiness probe failed: HTTP probe failed with statuscode: 503" at NGINX Insgress Controller pod in Kubernetes cluster
- Puma doesn't start the ruby on rails application immediately after puma started
- Custom path for "/actuator/health/liveness" and "/actuator/health/readiness" endpoints
- Spring Boot, deferring Readiness.ACCEPTING_TRAFFIC event?
- @Readiness and @Liveness annotations on methods using CDI does not work
- How to implement multiple handlers in readinessprobe
- Is there a way to define liveness probe API in Spring in a different port than the main one, while keeping the readiness probe in the default port?
- How can you specify an exec command with arguments in k8s deployment yaml?
- Spring boot default Liveness and Readiness probes
- kubernetes' readinessProbe prevents inter-pod communication during startup
- Can K8S pods marked as "Not ready" still receive direct requests?
- Pod restarting but i don't see any issues in the log
- Health and Liveness probe for Azure Web Jobs
- MySQL container liveness and readiness probes work but cause a lot of error logs in Kubernetes
- HTTP HEAD request /error triggers automatically for a spring boot application with health check configured
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Requests should still succeed if you use pod's IP address.
Readiness probes are used to determine if a pod is ready to receive traffic from kubernetes services, which if it's in "Not Ready" state, the pod shall not be included as endpoint or backend services.
Websocket is a communication protocol used in client-server communication like HTTP requests. HTTP probes are part of liveness and startup probes, wherein the kubelet will send a HTTP request in the specified path and port number to the pod's IP to perform a check.
Since it can be part of the liveness probe, it should not affect the readiness probe because it doesn't wait for it to succeed as stated from the official docs.