-
Notifications
You must be signed in to change notification settings - Fork 681
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
[flyteagent] Default Service Config Using Round Robin Mechanism #6179
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -40,9 +40,10 @@ var ( | |
}, | ||
}, | ||
DefaultAgent: Deployment{ | ||
Endpoint: "", | ||
Insecure: true, | ||
DefaultTimeout: config.Duration{Duration: 10 * time.Second}, | ||
Endpoint: "", | ||
Insecure: true, | ||
DefaultTimeout: config.Duration{Duration: 10 * time.Second}, | ||
DefaultServiceConfig: `{"loadBalancingConfig": [{"round_robin":{}}]}`, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Consider making service config configurable
Consider making the default service config more configurable by moving it to a separate constant or configuration option rather than hardcoding the round robin load balancing config directly in the default config struct. Code suggestionCheck the AI-generated fix before applying
Code Review Run #141009 Is this a valid issue, or was it incorrectly flagged by the Agent?
|
||
}, | ||
// AsyncPlugin should be registered to at least one task type. | ||
// Reference: https://github.com/flyteorg/flyte/blob/master/flyteplugins/go/tasks/pluginmachinery/registry.go#L27 | ||
|
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.
Consider if the endpoint URL
k8s://flyteagent.flyte:8000
should be configurable through a Helm value to support different namespace deployments.Code suggestion
Code Review Run #22c6ef
Is this a valid issue, or was it incorrectly flagged by the Agent?