-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add healthz liveness probe #2936
Conversation
Sets up a Ping healthz endpoint (ping) Adds a liveness probe to ansible operator deployment scaffolding
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just few nits which are :
- Add fragment
- Add comments to clarifies how/why the tests are made
Otherwise, it is :
/lgtm
/approve
but to take advantage of it, a liveness probe should be manually added | ||
to the operator manifest. See the | ||
[test operator](https://github.com/operator-framework/operator-sdk/blob/master/test/ansible/deploy/operator.yaml) | ||
for an example. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By following the doc standard it would be as;
migration:
header: **(Optional for Ansible-base operators)** Add livenessProbe check
body: >
Existing operators will have a healthz endpoint without intervention,
but to take advantage of it, a liveness probe should be manually added
to the operator manifest. Add the livenessProbe as the following example in the`/deploy/operator.ymal`
```ymal
livenessProbe:
httpGet:
path: /healthz
port: 6789
initialDelaySeconds: 5
periodSeconds: 3
```
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
based on previous discussions and quick re-review.
live_pod=$(kubectl get pod -l name=memcached-operator -o jsonpath="{..metadata.name}") | ||
if kubectl get events --field-selector involvedObject.name=$live_pod | grep Killing | ||
then | ||
error_text "FAIL: Operator pod killed due to failed liveness probe." | ||
kubectl get events --field-selector involvedObject.name=$live_pod,reason=Killing | ||
operator_logs | ||
exit 1 | ||
fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. I remember this discussion :) Looks like it worked.
Sets up a Ping healthz endpoint (ping)
Adds a liveness probe to ansible operator deployment scaffolding