-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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 startupProbe for Cilium-agent #14518
Conversation
@christarazi let me know if anything else is needed. Btw I didn't touch Also, as I have no "real-life" data of what could be a good timer, I fixed it to an arbitrary 300s (5 minutes) for the Regarding the |
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.
Few comments as per below.
I am wondering if the same can be done for preflight and hubble pods as well ? :thinking"
install/kubernetes/cilium/templates/cilium-agent-daemonset.yaml
Outdated
Show resolved
Hide resolved
install/kubernetes/cilium/templates/cilium-agent-daemonset.yaml
Outdated
Show resolved
Hide resolved
Hope you don't mind if I chime in. Currently, I think that as long as the value is greater or equal to current |
147365f
to
26bbd68
Compare
@sayboras Thanks for the review! I addressed the points. |
26bbd68
to
7e1de65
Compare
I think the delay is not that much for hubble or preflight, this can be addressed in separate PR as well. Feel free to remove WIP in PR description once you are ready. The current changes are LGTM 💯 |
install/kubernetes/cilium/templates/cilium-agent-daemonset.yaml
Outdated
Show resolved
Hide resolved
7e1de65
to
a3d4860
Compare
test-me-please |
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. Minor non-blocking nit
# Starting from Kubernetes 1.20, we are using startupProbe instead | ||
# of this field |
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.
# Starting from Kubernetes 1.20, we are using startupProbe instead | |
# of this field | |
# Starting from Kubernetes 1.20, we are using startupProbe instead | |
# of this field. |
Just to match with the rest of the formatting in the comment. A few occurrences of this.
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.
Fair point, fixed now.
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 💯
As of K8s 1.20, a new feature called startupProbe has been added. This allows to get better startup times especially for slow starting containers. Fixes cilium#14342 Signed-off-by: Youssef Azrak <yazrak.tech@gmail.com>
a3d4860
to
e2d1038
Compare
test-me-please |
test-gke |
1 similar comment
test-gke |
retest-net-next |
As of K8s 1.20, a new feature called startupProbe has been added.
This allows getting better startup times especially for slow starting
containers.
Fixes: #14342
Signed-off-by: Youssef Azrak yazrak.tech@gmail.com