healthcheck-dotnet-postgresql

You can add a PostgreSQL readiness health check by registering the Npgsql provider in your ASP.NET Core health checks pipeline. This automatically binds the connection string from configuration and tags the probe for the /health/ready endpoint.

A readiness health check validates if an application is prepared to handle traffic, such as confirming database connectivity. You need it for .NET backend deployments using orchestration platforms like Kubernetes to ensure traffic is only routed to healthy service instances.

No, the PostgreSQL health check does not require hardcoding the database connection string. It automatically retrieves and binds the correct database connection string from your application configuration to avoid exposing sensitive credentials.

Yes, you can use this skill to configure health probes for Kubernetes orchestration in .NET. It adds a /health/ready endpoint that validates PostgreSQL connectivity, ensuring Kubernetes only routes traffic to healthy service instances.

When the PostgreSQL database is unavailable during an ASP.NET Core readiness probe, the AddNpgSql extension method sets the failure status to Unhealthy. This status instructs orchestration tools to stop routing traffic to that service instance.