Add test_connection method to KubernetesHook#47881
Merged
jscheffl merged 5 commits intoapache:mainfrom May 11, 2025
Merged
Conversation
boring-cyborg
bot
added
area:providers
provider:cncf-kubernetes
fritz-astronomer
requested review from
hussein-awala and
jedcunningham
as code owners
Contributor
Author
|
@hussein-awala @jedcunningham (maybe @dimberman?) - any notes? |
jscheffl
approved these changes
May 11, 2025
Contributor
|
Looks good for me. LGTM! |
This was referenced May 14, 2025
sanederchik
pushed a commit
to sanederchik/airflow
that referenced
this pull request
Jun 7, 2025
* feat: add test_connection method to k8s hook * fix: update KubeHook to use kubernetes_conn_id * linting
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.
Adds a
test_connectionmethod (which could be utilized by #47082 )Should be the equivalent of
kubectl cluster-info, which is the lightest-weight way that I know of to test a connection.If others have better ideas for testing that a k8s cluster is reachable, that optimally requires little to no specific privileges on the cluster, please add a comment!