Open sopeal opened 4 years ago
Agree, it will help to make health check easier in K8s
+1
+1
+1
+1
@rayokota Feel free to copy my healthCheck logic from here - https://github.com/zalando-incubator/remora/pull/62/files#diff-2e8cc252e67c2ad91fb6519cc88f0f99R86
Thanks @cricket007, I'll take a look.
Any updates here?
What's wrong with /v1/metadata/id
?
It already returns 500 error when backing store is down
Any updates on this issue? It would be nice to have some way to healthcheck schema registry within Kubernetes.
@rodriguezconde See my previous comment
looks like /v1/metadata/id was protected once authentication enabled.
Is there a public endpoint that act as health check url?
/subjects
seems to be a better option
any update?
Hello,
I think adding a health check rest endpoint that verifies connection of depending services like kafka and zookeeper would bring value to schema registry.
I have schema registry managed by kubernetes cluster and I found out that sometimes schema registry loses connection to kafka. I can fix this problem by restarting a pod. Unfortunately there is no health check endpoint so restarting cannot be done automatically by kubernetes.
Is there any other solution which resolves that problem?