Agents docs updates #1475
Closed
Agents docs updates #1475
Conversation
This file contains 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
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
neverett
requested review from
EngHabu,
pingsutw and
ppiegaze
and removed request for
wild-endeavor and
kumare3
added 2 commits
February 1, 2024 16:06
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
3 tasks
added 2 commits
February 1, 2024 16:44
Signed-off-by: nikki everett <[email protected]>
Signed-off-by: nikki everett <[email protected]>
pingsutw
reviewed
Feb 5, 2024
|
|
||
| # Using Flyte agents in tasks | ||
|
|
||
| If you need to connect to an external service in your workflow, we recommend using the corresponding agent rather than a web API plugin. Unlike web API plugins, agents do not require creating a Kubernetes pod for each task. Agents are designed to be scalable and can handle large workloads efficiently, and decrease load on FlytePropeller, since they run outside of it. Finally, you can test agents locally without having to change the Flyte backend configuration, streamlining development. |
There was a problem hiding this comment.
web API plugin also won't create a Kubernetes pod for each task, but it has some drawbacks
- it's difficult to write a new plugin since data scientists or engineers are not familiar with Golang. (agent is written in Python)
- It's difficult to test the plugin locally. People have to update/build/deploy FlytePropeller, and deploy it to a remote cluster to test it.
- having to change the Flyte backend configuration (as you mentioned above)
Signed-off-by: nikki everett <[email protected]>
|
Closing this PR and adding these docs to this Flyte PR, since the contents of the /docs/getting_started directory have been moved to Flyte (see flyteorg/flyte#4814). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updated agents docs, structured as a guide aimed at end user and contributor audiences.
Staging docs
https://flyte--1475.org.readthedocs.build/projects/cookbook/en/1475/getting_started/agents.html
Related PRs
flyteorg/flyte#4822