Fix google gke system dag deprecations#69876
Open
viiccwen wants to merge 1 commit into
Open
Conversation
Contributor
Author
|
cc @shahar1, @henry3260. 🙌 |
Deprecated cluster-level fields cause example Dags to emit warnings when provider deprecations are enforced, including during serialization checks. Signed-off-by: viiccwen <vicwen@apache.org>
1bf5cc2 to
4847b3e
Compare
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
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.
Fixes a separate problem exposed after the Vertex AI Feature Store system Dag no longer blocked the generic import and serialization path.
Five Google Kubernetes Engine system Dags configured
initial_node_countat the cluster level, which the Google provider deprecates. They now configure the initial node count on an explicitdefault-poolnode pool. Existing Autopilot settings remain unchanged.closes #69825
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.