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
We'd like to have E2E tests for the pod restart policy.
The restart policy controls whether pods get restarted based on the exit code.
A simple E2E test would just be a simple script that exits with the desired code. We could then verify that the pod is restarted or not.
Verification might be a little tricky.
A simple way to do this would be:
The script can store state in shared storage
The test harness can verify that the correct state exists.
Some storage options
Adding this to the 0.2.0 release but it likely will be pushed to 0.3.
The text was updated successfully, but these errors were encountered:
https://github.com/gaocegege/k8s/tree/termination-example/examples/v1alpha2/restartpolicy
I used code here to test the PR #638
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
We'd like to have E2E tests for the pod restart policy.
The restart policy controls whether pods get restarted based on the exit code.
A simple E2E test would just be a simple script that exits with the desired code. We could then verify that the pod is restarted or not.
Verification might be a little tricky.
A simple way to do this would be:
The script can store state in shared storage
The test harness can verify that the correct state exists.
Some storage options
Adding this to the 0.2.0 release but it likely will be pushed to 0.3.
The text was updated successfully, but these errors were encountered: