Readiness probe failed: Get "http://<ip>:8080/login": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Contributing Jenkins Operator
1

Hello,
I am working with jenkins-operator 0.7.1. and jenkins:2.319.3-lts
I got the following error:
Warning Unhealthy 3s kubelet Readiness probe failed: Get “http://:8080/login”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)

in the value.yaml :

LivenessProbe for Jenkins Master pod

livenessProbe:
failureThreshold: 12
httpGet:
path: /login
port: http
scheme: HTTP
initialDelaySeconds: 80
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 5

ReadinessProbe for Jenkins Master pod

readinessProbe:
failureThreshold: 3
httpGet:
path: /login
port: http
scheme: HTTP
initialDelaySeconds: 30
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1

Can you please assist me?
Thanks,
Irina Rozalio

2

Just to manage expectations. We haven’t heard from virtus labs in a while now. No responses on GitHub, forums, and I’ve heard Thier OSS slack is dead quiet.

Also lts 319 is at least 6 months old.

I would recommend using the helm chart as it gets frequent updates and the community infra uaes it so it’s higher visibility

see:

1 Like
3

Thank you for your answer.
Could you please recommend me which version of jenkins-operator chart can I use? And which jenkins-maser version?
Could you please send me the link of the jenkins-operator updated chart?
Thanks a lot of!!!

4

No. As I said the operator is pretty abandoned. I don’t use it. I use the regular helm chart and it works pretty well

5

Great, Thanks Gavin, Could you please said me which helm chart jenkins you are using? Which version? And… could you please send me this helm chart link of the documentation?

Thanks a lot of!!!

6

Hi @Ira1 we recently merged some PR that should have fixed most of the operator issues, could you please try to deploy the operator version from master branch (still no new release yet).
Let me know :slight_smile: