[GH-ISSUE #472] Readiness endpoint #260

New Issue

zhus · 2026-04-08T16:51:34+03:00

zhus commented

2026-04-08 16:51:34 +03:00

Originally created by @j-vizcaino on GitHub (Oct 26, 2024).
Original GitHub issue: https://github.com/sigoden/dufs/issues/472

Specific Demand

Does dufs provide a readiness endpoint or URL that could be used in the context of Kubernetes? (or similar).

My local setup enforces authentication, and therefore the / URL returns a 401 status code, which leads Kubernetes into thinking the application is not ready.

Implement Suggestion

It is common practice for applications to provide either a separate port for readiness checks, or a dumb URL like /_ready or /_healthz/ready that simply returns OK text with a 200 HTTP status.

Thank you for developing and maintaining dufs: it is an amazing tool, simple and to the point. This clearly sets it apart of other bloated alternatives.

Originally created by @j-vizcaino on GitHub (Oct 26, 2024). Original GitHub issue: https://github.com/sigoden/dufs/issues/472 ## Specific Demand Does dufs provide a readiness endpoint or URL that could be used in the context of Kubernetes? (or similar). My local setup enforces authentication, and therefore the `/` URL returns a 401 status code, which leads Kubernetes into thinking the application is not ready. ## Implement Suggestion It is common practice for applications to provide either a separate port for readiness checks, or a dumb URL like `/_ready` or `/_healthz/ready` that simply returns `OK` text with a 200 HTTP status. Thank you for developing and maintaining `dufs`: it is an amazing tool, simple and to the point. This clearly sets it apart of other bloated alternatives.

zhus closed this issue

2026-04-08 16:51:34 +03:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: sigoden/dufs#260