-
Notifications
You must be signed in to change notification settings - Fork 518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QuarkusHealthCheckEnricher: default health path value is outdated in Quarkus 2.0.0.Final #758
Comments
rohanKanojia
changed the title
QuarkusHealthCheckEnricher: default health path value is wrong.
QuarkusHealthCheckEnricher: default health path value is outdated in Quarkus 2.0.0.Final
Jul 2, 2021
Related to: |
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Jul 8, 2021
… outdated Update default value of health path to `/q/health` Signed-off-by: Rohan Kumar <rohaan@redhat.com>
12 tasks
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Jul 9, 2021
… outdated QuarkusHealthCheckEnricher now reads quarkus properties related to rootPath, nonApplicationRootPath and health checks in order to evaluate health check endpoints for Quarkus versions greater than 1.11 Signed-off-by: Rohan Kumar <rohaan@redhat.com>
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Jul 9, 2021
… outdated QuarkusHealthCheckEnricher now reads quarkus properties related to rootPath, nonApplicationRootPath and health checks in order to evaluate health check endpoints for Quarkus versions greater than 1.11 Signed-off-by: Rohan Kumar <rohaan@redhat.com>
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Jul 12, 2021
… outdated QuarkusHealthCheckEnricher now reads quarkus properties related to rootPath, nonApplicationRootPath and health checks in order to evaluate health check endpoints for Quarkus versions greater than 1.11 Signed-off-by: Rohan Kumar <rohaan@redhat.com>
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Jul 13, 2021
… outdated QuarkusHealthCheckEnricher now reads quarkus properties related to rootPath, nonApplicationRootPath and health checks in order to evaluate health check endpoints for Quarkus versions greater than 1.11 Signed-off-by: Rohan Kumar <rohaan@redhat.com>
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Jul 13, 2021
… outdated QuarkusHealthCheckEnricher now reads quarkus properties related to rootPath, nonApplicationRootPath and health checks in order to evaluate health check endpoints for Quarkus versions greater than 1.11 Signed-off-by: Rohan Kumar <rohaan@redhat.com>
rohanKanojia
added a commit
to rohanKanojia/jkube
that referenced
this issue
Jul 13, 2021
… outdated QuarkusHealthCheckEnricher now reads quarkus properties related to rootPath, nonApplicationRootPath and health checks in order to evaluate health check endpoints for Quarkus versions greater than 1.11 Signed-off-by: Rohan Kumar <rohaan@redhat.com>
manusa
pushed a commit
that referenced
this issue
Jul 20, 2021
QuarkusHealthCheckEnricher now reads quarkus properties related to rootPath, nonApplicationRootPath and health checks in order to evaluate health check endpoints for Quarkus versions greater than 1.11 Signed-off-by: Rohan Kumar <rohaan@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
I was trying out @kameshsampath 's sample when I observed this, somehow pods were not coming in
Ready
state due to probe conditions not getting fulfilled. According to Quarkus docs[0], liveness healthchecks paths areHowever, when running
mvn k8s:resource
liveness/readiness probes are generated with this path:Looks like behavior in quarkus has changed and
/health/live
,/health/ready
URLs are no longer supported. I tested with another sample with Quarkus v1.13.7.Final and these were my observations:v1.13.7.Final
v2.0.0.Final:
[0] https://quarkus.io/guides/smallrye-health
Info
mvn -v
) :Kubernetes / Red Hat OpenShift setup and version :
If it's a bug, how to reproduce : run
mvn k8s:resource
in linked sampleIf it's a feature request, what is your use case :
Sample Reproducer Project : https://github.com/kameshsampath/istio-multi-rev-demo
The text was updated successfully, but these errors were encountered: