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 liveness and readiness to ingress and egress #1055
Changes from 3 commits
f8d7541
b611771
269f982
a1794ec
2c02881
9ad56b4
9557507
207466c
8b63f72
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1173,6 +1173,22 @@ spec: | |
ports: | ||
- containerPort: 80 | ||
- containerPort: 443 | ||
readinessProbe: | ||
exec: | ||
command: | ||
- curl http://localhost:15000/clusters && curl http://localhost:15000/listeners && curl http://localhost:15000/routes | ||
initialDelaySeconds: 3 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for putting this together. Are these numbers (seconds) default value? Just curious where we get this. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @andraxylia we should use There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. And also check if those endpoint return empty. |
||
periodSeconds: 5 | ||
timeoutSeconds: 3 | ||
failureThreshold: 10 | ||
livenessProbe: | ||
exec: | ||
command: | ||
- curl http://localhost:15000/clusters && curl http://localhost:15000/listeners && curl http://localhost:15000/routes | ||
initialDelaySeconds: 5 | ||
periodSeconds: 5 | ||
timeoutSeconds: 3 | ||
failureThreshold: 10 | ||
env: | ||
- name: POD_NAME | ||
valueFrom: | ||
|
@@ -1263,6 +1279,22 @@ spec: | |
- istio-mixer:9125 | ||
- --proxyAdminPort | ||
- "15000" | ||
readinessProbe: | ||
exec: | ||
command: | ||
- curl http://localhost:15000/clusters && curl http://localhost:15000/listeners && curl http://localhost:15000/routes | ||
initialDelaySeconds: 3 | ||
periodSeconds: 5 | ||
timeoutSeconds: 3 | ||
failureThreshold: 10 | ||
livenessProbe: | ||
exec: | ||
command: | ||
- curl http://localhost:15000/clusters && curl http://localhost:15000/listeners && curl http://localhost:15000/routes | ||
initialDelaySeconds: 5 | ||
periodSeconds: 5 | ||
timeoutSeconds: 3 | ||
failureThreshold: 10 | ||
env: | ||
- name: POD_NAME | ||
valueFrom: | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -70,6 +70,22 @@ spec: | |
ports: | ||
- containerPort: 80 | ||
- containerPort: 443 | ||
readinessProbe: | ||
exec: | ||
command: | ||
- curl http://localhost:15000/clusters && curl http://localhost:15000/listeners && curl http://localhost:15000/routes | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. why not use the standard http probe? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Right, this is another option, but we are running out of time for Monday morning. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually, this requires exposing port 15000. It is not a better option. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think performing checks without opening up new ports is preferred. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. the port is a good argument, I don't know how to configure it so it's only reachable from the probe so for readiness maybe this is a good approach, if it was actually checking something (which it isn't except for something listening on 15000) |
||
initialDelaySeconds: 3 | ||
periodSeconds: 5 | ||
timeoutSeconds: 3 | ||
failureThreshold: 10 | ||
livenessProbe: | ||
exec: | ||
command: | ||
- curl http://localhost:15000/clusters && curl http://localhost:15000/listeners && curl http://localhost:15000/routes | ||
initialDelaySeconds: 5 | ||
periodSeconds: 5 | ||
timeoutSeconds: 3 | ||
failureThreshold: 10 | ||
env: | ||
- name: POD_NAME | ||
valueFrom: | ||
|
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.
1 url should be enough for a liveness check no? (Does envoy have a /ready or one of those is the last one ready)
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.
you are right, one is enough, will change.
It does not have /ready, we can suggest an improvement.