ISSUE TYPE
SUMMARY
Current deployment does not include any livenessProbes or readinessProbes for the containers.
This leads to issues with the Deployment, as it just replaces all pods nearly at the same time and does not wait, until an exchanged pod is ready yet. Therefore AWX may not be reachable temporarily.
This is especially problematic if the user added a configuration error via any of the AWX-options, such as extra-config/custom.py or database-config.
ENVIRONMENT
- AWX version: 21.0.0
- Operator version: 0.21.0
- Kubernetes version: 1.22.9
- AWX install method: Kubernetes via awx-operator
STEPS TO REPRODUCE
- deploy awx-operator & AWX as described in README.md
- verify, that AWX works
- change configuration of AWX resource
- wait for awx-operator to apply new deployment
EXPECTED RESULTS
- K8s deployment gracefully stops each pod and deploys another one sequentially, without downtime
ACTUAL RESULTS
- K8s deployment stops each pod nearly at the same time, as new pods are marked as ready even when they are not yet
- a downtime can be experienced
ADDITIONAL INFORMATION
AWX-OPERATOR LOGS
ISSUE TYPE
SUMMARY
Current deployment does not include any
livenessProbesorreadinessProbesfor the containers.This leads to issues with the Deployment, as it just replaces all pods nearly at the same time and does not wait, until an exchanged pod is ready yet. Therefore AWX may not be reachable temporarily.
This is especially problematic if the user added a configuration error via any of the AWX-options, such as extra-config/custom.py or database-config.
ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
ADDITIONAL INFORMATION
AWX-OPERATOR LOGS