e2e: Fix fluentd test for AL2023, and for CI using OIDC #155
+163
−26
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mumoshu
force-pushed
the
fix-fluentd-e2e-oidc-and-al2023
branch
from
50d4a7d to
c3a0db4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes the E2E test for the fluentd checker to work with AL2023-based managed node groups by explicitly setting
http_put_response_hop_limit.This also fixes the issue on CI where you can't persist the tfstate(!). The default tf project assumes you use S3 backend now. The terraform
backend-configlike the bucket name and the object key for the tfstate should be provided via envvars.