Fix flaky e2e test and add support for enabling apiserver debug logs during testing #250
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
There seems to be a race condition inside the apiserver where k8s-shredder is able to evict pods even if the pdb wouldn't allow soft evictions.
Not sure if it is related to the kind cluster or a real issue inside the apiserver codebase.
This PR adds an extra check to make sure that the PDB status associated with the rollout object is properly populated.
This PR also adds support to enabled apiserver debug logs during trubleshooting by using the
ENABLE_APISERVER_DEBUG
env var.Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: