We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Based on a remark in #167 (comment).
For example if a kubectl command fails to look up zone identifier, due to a transient error, we'd get one pod without the rack awareness support.
The text was updated successfully, but these errors were encountered:
Exit non-zero, i.e. restart, on any init script error
fea6915
Fixes #168, possibly avoiding unexpected states for example at transient kubectl errors
No branches or pull requests
Based on a remark in #167 (comment).
For example if a kubectl command fails to look up zone identifier, due to a transient error, we'd get one pod without the rack awareness support.
The text was updated successfully, but these errors were encountered: