Red Hat Bugzilla – Bug 1274136
[DOCS] High-level application health checks section needs more info
Last modified: 2018-05-08 20:30:39 EDT
The section on high-level application health checks can do with more details:
- needs an example
- which components would need to be tested?
- what actions would need to be taken if it fails?
- how does OpenShift facilitate these high-level checks?
- how do you specify the check and response?
This BZ comes out of this PR:
Today we have a few options to complete this.
1: Implement a pod level script that while checking the health of a pod also checks the health of the
application as a whole.
- Note, this is not what we want to recommend but it is currently he most viable solution, and is
the simplest one to implement. It should be noted that this could be implemented as a "monitor"
pod, completely outside of the application as well.
2: Implement a maintenance or health check Job . This container or image can be used, to preform
the checks that an entire application is up and working as you would expect.
- Note, while one job is great an will meet the need, it really only becomes helpful if the job can
be scheduled , or kicked off regularly. So until this is worked into the product (Kubernetes)
this solution is limited.
@Brice - can this be a part of the new Day 2 guide?
Vikram, I'll agree that the Day Two Guide fulfills this BZ.
The current section that I initially intended to be elaborated on mentions consulting with the admin to create health checks. This PR is for the day two guide:
I don't thin it's necessary to do anything else with the content. I'll close this BZ.
If there's any disagreements, let me know.