Update 'namespace' priority for 'find_pod' function #43762
Merged
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.
In this PR I have updated the
namespacepriority for thefind_podfunction. Because we faced the bug, in case when the user specifiednamespacein the task and inside the metadata forpod_request_objuser has a different namespace. Thennamespacewill be overwritten by the value which is specified in the task. This priority looks incorrect, because in thefind_podfunction we need to find a Pod which has already started. And information about this Pod inside thepod_request_objvariable. It means that firstly we need to check value inpod_request_obj.metadata.namespaceand, then, value insideself.namespace.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.