# Jenkins says it's fully up and running but then dies in minikube, any help appreciated

**URL:** <https://community.jenkins.io/t/jenkins-says-its-fully-up-and-running-but-then-dies-in-minikube-any-help-appreciated/5373>\
**Category:** Jenkins Operator\
**Tags:** question\
**Created:** [January 19, 2023, 11:59am UTC](https://community.jenkins.io/t/jenkins-says-its-fully-up-and-running-but-then-dies-in-minikube-any-help-appreciated/5373 "2023-01-19T11:59:50Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![halkeye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/halkeye/32/8_2.png) [@halkeye](https://community.jenkins.io/u/halkeye)\
**Post date:** [January 19, 2023, 5:49pm UTC](https://community.jenkins.io/t/jenkins-says-its-fully-up-and-running-but-then-dies-in-minikube-any-help-appreciated/5373/3 "2023-01-19T17:49:52Z")

</div>

just a heads up

> [@Readiness probe failed: Get "http://\<ip\>:8080/login": context deadline exceeded (Client.Timeout exceeded while awaiting headers)](https://community.jenkins.io/t/readiness-probe-failed-get-http-ip-8080-login-context-deadline-exceeded-client-timeout-exceeded-while-awaiting-headers/4978/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:

---

_[View the full topic](https://community.jenkins.io/t/jenkins-says-its-fully-up-and-running-but-then-dies-in-minikube-any-help-appreciated/5373)._