-
Notifications
You must be signed in to change notification settings - Fork 343
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
docs: add best practice docs to avoid race condition bw kubelet and apisix #2045
Conversation
…pisix Signed-off-by: Ashish Tiwari <ashishjaitiwari15112000@gmail.com>
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 a few minor formatting suggestions
docs/en/latest/tutorials/how-to-avoid-race-condition-when-scaling-down.md
Outdated
Show resolved
Hide resolved
docs/en/latest/tutorials/how-to-avoid-race-condition-when-scaling-down.md
Outdated
Show resolved
Hide resolved
docs/en/latest/tutorials/how-to-avoid-race-condition-when-scaling-down.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Traky Deng <trakydeng@gmail.com>
lifecycle: | ||
preStop: | ||
exec: | ||
command: ["/bin/sh", "-c", "sleep 5 && kill -SIGTERM $(cat /var/run/webserver.pid)"] |
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.
This user case is not concise enough and misleading. I think just writing sleep 5 is enough. It means that sleep 5 gives the apisix ingress controller enough time to process the control plane changes.
@Sn0rt I applied the suggestion. PTAL |
Type of change:
Fixes #2030
What this PR does / why we need it:
Pre-submission checklist: