health-checks | Laravel health checker | Monitoring library

I am trying to deploy a mastodon server using this project: https://github.com/tootsuite/mastodon

I am running Docker-Compose and Podman on a Fedora 33 server.

In Google Cloud blog they say that if Readiness probe fails, then traffic will not be routed to a pod. And if Liveliness probe fails, a pod will be restarted.

Kubernetes docs they say that the kubelet uses Liveness probes to know if a container needs to be restarted. And Readiness probes are used to check if a container is ready to start accepting requests from clients.

My current understanding is that a pod is considered Ready and Alive when all of its containers are ready. This in turn implies that if 1 out of 3 containers in a pod fails, then the entire pod will be considered as failed (not Ready / not Alive). And if 1 out of 3 containers was restarted, then it means that the entire pod was restarted. Is this correct?

I have an ECS cluster with multiple nodes (task defs) fronted by an application load balancer. Does it make sense to configure a health check at the load balancer and at the container level (within the task definition)?

The load balancer runs the configured health check against every registered target so it can unregister failing nodes. Setting the health check at the container level accomplishes the same thing: ECS will unregister any container that fails the health check (according to your configuration). ECS will always instantiate more instances of your task def to satisfy your desired count.

To me it sounds like if your task definition only has a single container, then only setting the health check at the load balancer (since it's required) is enough. Am I missing anything?

I was learing about HealthChecks following the information posted on the MSDN site: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/health-checks?view=aspnetcore-5.0#register-health-check-services

The following code snippet tells that if an unhealthy checks returns I can overwrite the value by saying it's degraded instead.

I'm evaluating the use of Microsoft Health Checks to improve routing of our internal load balancer. So far I'm very happy with the functionality provided by this feature and the community around it. However there's one thing I did not find yet and wanted to ask if it is possible out of the box:

The Health Checks seem to retrieve their own status as soon as they are requested. But because our service might have a hard time processing a lot of request in that given moment, the query to a thrid-party component like the SQL Server might take it's time to respond. Therefore, we would like to pre-evaluate that health check periodically (like every few seconds) and return that state when the health check api gets called.

The reason is, that we want our load balancer to get the health state as quickly as possible. Using pre-evaluated results seems to be good enough for our use case.

Now the question is: Is it possible to add a kind of "poll" or "auto-update" mechanism to the ASP.NET Core health checks? Or does this mean I have to implement my own health check returning values from a background service which pre-evaluates the results periodically?

Please note, I want to use pre-evaluated results on each request which is NOT HTTP Caching where the live result is cached for the next requests.

I've a golang program which I need to add a new call to the K8S API server status (livez) api to get the health status.

https://kubernetes.io/docs/reference/using-api/health-checks/

The program should run on same cluster of the api server and need to get the /livez status, I've tried to find this API in client-go lib but didn't find a way to achieve it...

https://github.com/kubernetes/client-go

Is there a way to do it from Go program which is running on the same cluster that the API server run?

I was reading this article https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/health-checks?view=aspnetcore-3.1#filter-health-checks and couldn't visualize a practical use case for using filter health checks. In a real world situation, when would I use this? Thanks!

I've configured health checks using the middleware in an MVC application, but have been asked to enforce https on the health endpoint for security reasons. For separate reasons, I can't enforce it across the service as a whole, and so I was wondering if there was a mechanism to selectively do this to just the health endpoint. While it's possible to do this with a controller, but I can't seem to achieve it for the endpoint created by the middleware.

Is there any built-in way to achieve this? Could I create some sort of custom middleware as a wrapper to achieve it?

I've looked into EndpointBuilders, conventions, RequireHttps, and more, but have been unable to find anything.

My Configuration is same as below.