[ENH] - Provide a liveliness check for storage
- Dominant language
- Mustache
- Stars
- 55
- Forks
- 68
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
CouchDB provided an error on Read-Only storage but did not trigger the readiness check on the _up endpoint (default provided readiness check).
**Describe the solution you'd like**
I propose the current readiness check be moved to liveliness and readiness be similar to sh -c 'touch /opt/couchdb/data/.ready'. If it exits != 0 for storage issues the pod will reset which would trigger a storage mount refresh.
**Describe alternatives you've considered**
I've made this change in local system. It works.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the chart's Kubernetes probe configuration and compare the current _up readiness check with the proposed liveness check. Review how the /opt/couchdb/data/.ready touch command would represent storage readiness, then verify that a nonzero result causes the intended pod restart and that readiness remains separate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100