This repository has been archived by the owner on Jun 19, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 202
Option to Disable Liveness/readiness checks #1444
Labels
cat/feature
Feature request
Comments
This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions! |
rohanKanojia
added a commit
to rohanKanojia/fabric8-maven-plugin
that referenced
this issue
Mar 12, 2019
+ Added an option fabric8.disableHealthChecks to disable readiness/liveness checks + Added path option in SpringBootHealthCheckEnricher to overwrite path for liveness/readiness
rohanKanojia
added a commit
to rohanKanojia/fabric8-maven-plugin
that referenced
this issue
Mar 12, 2019
+ Added an option fabric8.disableHealthChecks to disable readiness/liveness checks + Added path option in SpringBootHealthCheckEnricher to overwrite path for liveness/readiness
rohanKanojia
added a commit
to rohanKanojia/fabric8-maven-plugin
that referenced
this issue
Mar 13, 2019
+ Added an option fabric8.disableHealthChecks to disable readiness/liveness checks + Added path option in SpringBootHealthCheckEnricher to overwrite path for liveness/readiness
rohanKanojia
added a commit
that referenced
this issue
Mar 13, 2019
+ Added an option fabric8.disableHealthChecks to disable readiness/liveness checks + Added path option in SpringBootHealthCheckEnricher to overwrite path for liveness/readiness
@Na3blis : Could you please try 4.0.0 out and see if it is working as per your use case? |
That's what I was looking for, thanks! |
@Na3blis : Did it work according to your use case? |
Yep, that resolved the issues. Both options actually were good, and resolved my issues when testing |
good to hear ;-) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I need to be able to disable the actuator enricher, or be able to overwrite the path that it checks for both liveness and readiness
Info
mvn -v
) : 3.6.0minikube v0.30.0
My project uses custom JWTs to secure endpoints. K8 is not able to access the standard actuator endpoints, and so we have created custom endpoints for liveness/readiness checks that are open for k8. However, since we have actuator on the classpath, f-m-p adds liveness and readiness checks that will always fail because k8 gets a 403 error.
The text was updated successfully, but these errors were encountered: