-
Notifications
You must be signed in to change notification settings - Fork 57
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
HttpGet Readiness Probe causes a deadlock #73
Milestone
Comments
@PeterRockstars, |
This issue is fixed and will be released in the next release. |
Fantastic! Do you know yet when the next release will be? |
@PeterRockstars, |
So polite! Thanks 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using https://github.com/dotnet-architecture/HealthChecks.
When an HttpGet Readiness Probe is configured, either Application Insights Kubernetes fails to start, or the pod never gets to Ready.
Steps to reproduce:
add this to deployment.yaml:
This will cause the pod to be ready after 130 seconds, but the logs show:
When the probe is defined like this:
the pod never reaches ready state and gives an error:
The logs show that the application never initialises further than this message:
A possible solution might be to wrap the initialisation in a Task.Run(), as is done for retrieving the version info in
KubernetesModule.EnableKubernetes
The text was updated successfully, but these errors were encountered: