Adding kubernetes provider upgrade statement in Dockerfile #1235
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
vatsrahul1001
requested review from
phanikumv,
pankajastro,
pankajkoti,
Lee-W,
sunank200 and
utkarsharma2
as code owners
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #1235 +/- ##
=======================================
Coverage 98.58% 98.58%
=======================================
Files 90 90
Lines 5389 5389
=======================================
Hits 5313 5313
Misses 76 76 ☔ View full report in Codecov by Sentry. |
|
Should we deploy this branch to the astro cloud for testing before we merge it? |
pankajkoti
approved these changes
Jul 10, 2023
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.
We have recently observed that after the latest Airflow Provider Release, our deployment does not have the latest Kubernetes providers. However, for other providers like the Google provider, we have the latest version. As a result, our
example_google_kubernetes_engineDAG is experiencing parsing issues, as per discuss we decided to upgrade k8s provider explicitly in out docker fileMore context here