Surface DB/S3 health check connection errors to DSPA cr #451
Labels
good first issue
Good for newcomers
priority/low
An issue with the product that doesn't impact the user much or not at all (ie tech debt)
triage/accepted
description
For example the x509 errors that we may encounter when doing health checks should be added to the DSPA status CR.
Currently these errors are hidden from the user and require investigating the DSPO logs for information, we should expose these types of errors to the health check conditions for the ocp project user.
The text was updated successfully, but these errors were encountered: