Skip to content

PROJQUAY-5074: docs: add storage health check configuration fields#1667

Open
Rachimypala-RM wants to merge 1 commit into
quay:masterfrom
Rachimypala-RM:PROJQUAY-5074-storage-health-check-docs
Open

PROJQUAY-5074: docs: add storage health check configuration fields#1667
Rachimypala-RM wants to merge 1 commit into
quay:masterfrom
Rachimypala-RM:PROJQUAY-5074-storage-health-check-docs

Conversation

@Rachimypala-RM

Copy link
Copy Markdown

Add documentation for three new configuration parameters introduced to improve health check coverage for storage engines:

  • HEALTH_CHECKER_INSTANCE_CHECK_PREFERRED_STORAGE: enables preferred storage validation on /health/instance for Kubernetes liveness probes
  • DISTRIBUTED_STORAGE_VALIDATE_ENDTOEND: enables validation of all configured storage engines on /health/endtoend instead of only the preferred engine
  • DISTRIBUTED_STORAGE_REQUIRES_ALL_AVAILABLE: controls whether any single engine failure or all-engine failure triggers a 503 response

Updates health-check-quay.adoc with new endpoint behavior descriptions and example JSON outputs. Creates a new config-fields-health-check.adoc reference module and wires it into config_quay/master.adoc.

Add documentation for three new configuration parameters introduced
to improve health check coverage for storage engines:

- HEALTH_CHECKER_INSTANCE_CHECK_PREFERRED_STORAGE: enables preferred
  storage validation on /health/instance for Kubernetes liveness probes
- DISTRIBUTED_STORAGE_VALIDATE_ENDTOEND: enables validation of all
  configured storage engines on /health/endtoend instead of only the
  preferred engine
- DISTRIBUTED_STORAGE_REQUIRES_ALL_AVAILABLE: controls whether any
  single engine failure or all-engine failure triggers a 503 response

Updates health-check-quay.adoc with new endpoint behavior descriptions
and example JSON outputs. Creates a new config-fields-health-check.adoc
reference module and wires it into config_quay/master.adoc.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
[id="config-fields-health-check"]
= Storage health check configuration fields

The following configuration fields control how {productname} validates storage engine availability during health checks. These fields allow you to tune the `GET /health/instance` and `GET /health/endtoend` endpoints for geo-replicated deployments and Kubernetes liveness probes.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would say this suits better the readiness probe instead of liveness.

[source,yaml]
----
# ...
# Add preferred_storage check to /health/instance (recommended for Kubernetes liveness probes)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as before, dependencies should be checked in readiness, not liveness.

@lechuk47

Copy link
Copy Markdown

@kleesc Since you introduced this feature, could take an additional look please? I may be missing context on why this was added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants