Additional custom liveness probe for storage.

[ghorofamike]

Custom storage can have issues, and it would be useful to be able to tell when arangodb containers need to be restarted, such as when the storage is remounted read-only on the containers, and we have to kill it and restart it. At the moment, if the storage becomes read only, arango keep running, and logs an error when a write is attempted and fails, would be nice if we could have a liveness probe for this, that could look like:

...
spec:
  *restartPolicy: Always*
  containers:
  - name: arango-crdn
      ...
      *livenessProbe*:
      exec:
        command:
        - ls
        - /data/lost+found
      initialDelaySeconds: 5
      periodSeconds: 10

[ajanikow]

Hello!

Check will be now part of ArangoDB standard probe, will update issue with fixed versions.

Best Regards,
Adam.

[ghorofamike]

will update issue with fixed versions.
Adam.
@ajanikow
Has a PR for this hit the repo yet?

[ghorofamike]

@ajanikow is this addressed in the latest release?