Open agwermann opened 1 year ago
fyi @claudio4j @christophd
@claudio4j @christophd @squakez Were you able to reproduce the issue? Do you have some workaround for it?
I was able to reproduce the readiness failure. When running the integration in a knative enabled profile, by default any http consumer is materialized as a knative service and after some inactivity period (no incoming http requests into the http endpoint) the integration pod is shutdown. Because of this the readiness probe may have failed due to the pod being inactive for a short period of time. When there is a new http request, the pod is started and there are only 3 readiness failures while the pod is up.
Readiness: http-get http://:8012/ delay=0s timeout=1s period=10s #success=1 #failure=3
Perhaps we could tweak the readiness probe configuration to allow more time or increase the failureThreshold.
This issue has been automatically marked as stale due to 90 days of inactivity. It will be closed if no further activity occurs within 15 days. If you think that’s incorrect or the issue should never stale, please simply write any comment. Thanks for your contributions!
Description
I am getting a readiness probe failure in the knative
queue-proxy
sidecar when running the below Camel-k DSL in k8s cluster. The DSL exposes a POST endpoint and publishes the message into a MQTT topic using paho. The DSL works fine when running locally usingkamel run local
command.Environment
Kubernetes: v1.23.8 Knative: v1.18 Camel-k: 1.10.3
Steps to reproduce
Run
kamel run MQTTResponseHandler.java
. You should be able to reproduce the issue.Logs
kubectl describe pod mqtt-response-handler-00001-deployment-c54965496-v7jl6
kubectl logs mqtt-response-handler-00001-deployment-c54965496-v7jl6 queue-proxy
kubectl logs camel-k-operator-846cb65cfb-cg4ls