Update flaky volume toleration regex to include projected volumes #99898
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.
What type of PR is this?
/kind flake
What this PR does / why we need it:
Injected service account tokens changed from secret-based to projected-token based by default in #95667, which merged 2/18
That coincides with this flake starting: https://storage.googleapis.com/k8s-gubernator/triage/index.html?date=2021-02-27&text=volumes%2Fkubernetes.io~projected
This test already tolerated secret volume setup errors, until #88766 is resolved. The regex should be expanded to accomodate projected volume tokens until that issue is resolved.
Which issue(s) this PR fixes:
Fixes #99599
/cc @zshihang @smarterclayton @jkaniuk @ehashman