Liveness and Readiness probes failing
See original GitHub issueHello!
First of all, congrats to you all, kafka-ui is such a nice project!
We wrote a Helm Chart to deploy Kafka UI in a Kubernetes cluster, using version 0.3.0.
We are facing the following issue when using liveness and readiness probes in the k8s deployment:
Readiness probe failed: HTTP probe failed with statuscode: 404
Even using different paths like /actuator/health
, /actuator/info
and login
that are declared here the probes are failing. Also, we checked the Helm Chart deployment you provided.
Set up
- Kafka UI - Version: 0.3.0
- Docker image: provectuslabs/kafka-ui:0.3.0
- The Helm Chart applied in the cluster has the following liveness and readiness probes:
ports:
- name: view
containerPort: 8080
protocol: TCP
livenessProbe:
httpGet:
path: /actuator/health
port: view
initialDelaySeconds: 60
periodSeconds: 30
timeoutSeconds: 10
readinessProbe:
httpGet:
path: /actuator/health
port: view
initialDelaySeconds: 60
periodSeconds: 30
timeoutSeconds: 10
Removing the probes, it is possible to use Kafka UI normally in an integration environment in Kubernetes cluster, but we really need the probes before deploying in production.
Thanks a lot!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Configure Liveness, Readiness and Startup Probes
At the bottom of the output, there are messages indicating that the liveness probes have failed, and the failed containers have been killed...
Read more >Kubernetes Liveness and Readiness Probes: How to Avoid ...
Recall that a liveness-probe failure will result in the container being restarted. Unlike a readiness probe, it is not idiomatic to check ...
Read more >You (probably) need liveness and readiness probes
When a readiness probe fails, it indicates to OpenShift that the container being probed is not ready to receive incoming network traffic. The ......
Read more >Kubernetes Readiness probe failed error - Stack Overflow
js application and I am trying to manage it through minikube. readinessProbe failure - k8s will not route traffic to pod; livenessProbe failure ......
Read more >Readiness probe fails if the container restarts after a liveness ...
After a liveness probe fail, the container should restart and ideally should start serving the traffic again, just like how it would happen...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@nandacamargo thanks much for the detailed feedback! This is to be fixed within #1339 and we’ll release a separate build shortly after.
Great! Thank you so much!