Remove checks for 1.19 api checks#28461
Merged
jedcunningham merged 1 commit intoapache:mainfrom Dec 19, 2022
Merged
Conversation
There were checks for Kubernetes API >= 1.19 for ingress and they are not needed any more since we support 1.23+ only. This was actually harmful in some cases as the checks were not perfect and caused failures in somke k8s implementations (microk8s for example). Fixes: apache#22657
jedcunningham
approved these changes
Dec 19, 2022
28 tasks
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
2 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.
There were checks for Kubernetes API >= 1.19 for ingress and they are not needed any more since we support 1.23+ only.
This was actually harmful in some cases as the checks were not perfect and caused failures in somke k8s implementations (microk8s for example).
Fixes: #22657
^ 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.