You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there any possibility of having a health check for use in Kubernetes? We've seen that when using iceberg-rest with PostgreSQL if the connection to the database server drops, the iceberg-rest server needs rebooting. This could be easily handled automatically from Kubernetes by having a health check but I don't know how much effort it would be to add in health checks for each catalog (where necessary)
The text was updated successfully, but these errors were encountered:
I think what you probably want to do is just create a table and point the healthcheck at the load endpoint.
Typically this would be something like default.dual and then just have k9s load the table via the REST endpoint. That would touch the database and ensure liveness.
Alternatively, you could use the list namespaces, since that doesn't require the existence of a table.
Is there any possibility of having a health check for use in Kubernetes? We've seen that when using
iceberg-rest
with PostgreSQL if the connection to the database server drops, theiceberg-rest
server needs rebooting. This could be easily handled automatically from Kubernetes by having a health check but I don't know how much effort it would be to add in health checks for each catalog (where necessary)The text was updated successfully, but these errors were encountered: