-
Task
-
Resolution: Done
-
L3 - Default
-
None
-
None
-
Not defined
Context:
With OPT-4264 a readiness endpoint was introduced to the rest api of Optimize which allows to track whether an Optimize container is in an operating state, also see https://docs.camunda.org/optimize/latest/technical-guide/rest-api/health/.
AT:
- all existing k8s deployement descriptors used for test environments should make use of this endpoint for `readiness/liveness` probes https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
- on instabilities are ideally alerts sent to #optimize-ci-alerts on slack so we are aware of them
This is the controller panel for Smart Panels app
[OPT-4812] Make use of /api/ready endpoint in all optimize k8s descriptors
| Description |
Original:
Context:
With AT: - all existing k8s deployement descriptors used for test environments should make use of this endpoint for `readiness/liveness` probes https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ - ideally alerts are sent to #optimize-ci-alerts on slack so we are aware of any instabilities |
New:
Context:
With AT: - all existing k8s deployement descriptors used for test environments should make use of this endpoint for `readiness/liveness` probes https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ - on instabilities are ideally alerts sent to #optimize-ci-alerts on slack so we are aware of them |
| Mentioned Roles |
| Mentioned Groups |
| Status | Original: Open [ 1 ] | New: In Specification [ 10000 ] |
| Labels | Original: current_release | New: next_release |
| Labels | Original: next_release | New: current_release next_release |
| Labels | Original: current_release next_release | New: current_release |
| Labels | Original: current_release | New: next_release |
| Reporter | Original: Sebastian Bathke [ sebastian.bathke ] | New: Andromachi Rozaki [ andromachi.rozaki ] |