Add a feature for health checks (readiness and liveness) for Ansible Tower
- Dominant language
- Python
- Stars
- 15.6k
- Forks
- 3.7k
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 25
Description
##### ISSUE TYPE
- Feature Idea
##### SUMMARY
Many applications running for long periods of time eventually transition to broken states, and cannot recover except by being restarted. Kubernetes provides liveness probes to detect and remedy such situations. [1]
Here the ask is to provide this to avoid manual operation task such as restart the containers/pods. The current tarball [2] only provides these probes for postgres and not for the other containers (redis, memcached, tower-web, tower-task).
[1] https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
[2] https://releases.ansible.com/ansible-tower/setup_openshift/ansible-tower-openshift-setup-3.7.1-1.tar.gz
Contributor guide
Research direction
Start with the Kubernetes liveness, readiness, and startup probe documentation and inspect the referenced ansible-tower-openshift-setup-3.7.1-1.tar.gz, comparing its PostgreSQL probes with the missing coverage for redis, memcached, tower-web, and tower-task. Done means the requested health checks are defined for those containers and can support automatic restart or readiness handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100