Add unauthenticated /healthz endpoint - #174
Open
neverlless wants to merge 1 commit into
Open
Conversation
Checks session storage and FreeIPA connectivity, returns JSON status. Registered before the CSRF middleware so monitoring probes don't create sessions or log 'Login required' errors.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
There is currently no way to health-check mokey without hitting authenticated pages: probing
/(Kubernetes probes, blackbox_exporter, uptime monitors) redirects to login, logsLogin required and no authenticated session foundon every probe, and — because the CSRF middleware saves a session on every GET — creates a new session storage entry per probe.Changes
GET /healthzendpoint returning200 {"status":"ok"}when healthy, or503with the failing component when the session storage backend or FreeIPA is unreachable (usesstorage.Getand the admin client'sPing()).Testing
Running in production as Kubernetes startup/readiness probe and blackbox_exporter target:
Log spam from probes is gone, and no per-probe sessions accumulate in redis anymore.