Fix k8s flaky test - JWT secret might be different #47765
Merged
Conversation
This file contains hidden or 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
Lee-W
added
the
full tests needed
potiuk
approved these changes
Mar 14, 2025
Member
|
One of the k9S tests failed, but this was a dffferent reason - looked like regular "failure" of the infrastructure. Merging. |
agupta01
pushed a commit
to agupta01/airflow
that referenced
this pull request
Mar 21, 2025
nailo2c
pushed a commit
to nailo2c/airflow
that referenced
this pull request
Apr 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
related: #47532 (comment)
What
Ensure that
[api/auth_jwt_secret]inairflow.cfgis consistent in the Kubernetes ConfigMap for theairflow-api-serverdeployment.