Skip to content
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.

Sign up for GitHub

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

tests: Potentially fix flaky ValidtionStrict test #10598

Closed
wants to merge 1 commit into from
Closed

tests: Potentially fix flaky ValidtionStrict test #10598

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions changelog/v1.19.0-beta6/fix-validation-strict.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
changelog:
- type: NON_USER_FACING
description: Potentially fix the flaky ValidationStrct test by ensuring the kubeCoreFailurePolicy is set to Fail

1 change: 1 addition & 0 deletions test/kubernetes/e2e/tests/manifests/validation-strict-helm.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,7 @@ gateway:
validation:
enabled: true
failurePolicy: Fail # For "strict" validation mode, fail the validation if webhook server is not available
kubeCoreFailurePolicy: Fail # For "strict" validation mode, fail the validation if webhook server is not available
allowWarnings: false # For "strict" validation mode, webhook will also reject warnings
alwaysAcceptResources: false
# added to preserve behavior tested by this suite.
Expand Down
Loading