-
Notifications
You must be signed in to change notification settings - Fork 674
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Print K8s Resolver Event for Agent Grpc request debugging #6146
base: master
Are you sure you want to change the base?
Print K8s Resolver Event for Agent Grpc request debugging #6146
Conversation
Signed-off-by: Future-Outlier <eric901201@gmail.com>
Code Review Agent Run #37ddb4Actionable Suggestions - 0Review Details
|
Changelist by BitoThis pull request implements the following key changes.
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #6146 +/- ##
=======================================
Coverage 37.01% 37.02%
=======================================
Files 1317 1317
Lines 132523 132534 +11
=======================================
+ Hits 49060 49066 +6
- Misses 79217 79221 +4
- Partials 4246 4247 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you for adding this
flytestdlib/resolver/k8s_resolver.go
Outdated
@@ -166,6 +177,11 @@ func (k *kResolver) run() { | |||
case <-k.ctx.Done(): | |||
return | |||
case event, ok := <-watcher.ResultChan(): | |||
logger.Info(k.ctx, "k8s resolver watchet event response: [%v]", event) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will it print the event.Object
? If so, I think we can remove line 181 and 182
Code Review Agent Run #6076daActionable Suggestions - 0Review Details
|
Tracking issue
#3936
Why are the changes needed?
k8s resolver might fail if we set the wrong deployment endpoint for
agent service
, print what error happened will be super helpful.What changes were proposed in this pull request?
print service namespace, service name, and response event.
How was this patch tested?
build a propeller image and tested in private cluster.
Setup process
Screenshots
Check all the applicable boxes
Related PRs
Docs link
Summary by Bito
Enhanced Kubernetes resolver logging in Flyte standard library by implementing detailed error logging for watcher creation failures and adding comprehensive logging for Kubernetes watcher events. Added service namespace and service name details to log messages, fixed typos, and removed redundant log statements for more concise and accurate debug information. The changes improve debugging capabilities by providing visibility into event responses, object details, and object kinds.Unit tests added: False
Estimated effort to review (1-5, lower is better): 1