-
Notifications
You must be signed in to change notification settings - Fork 660
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'origin' into fix-flytectl-install-script
Signed-off-by: Eduardo Apolinario <[email protected]>
- Loading branch information
Showing
6 changed files
with
49 additions
and
48 deletions.
There are no files selected for viewing
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -133,21 +133,20 @@ class FileSensor(BaseSensor): | |
|
||
### 2. Test the agent | ||
|
||
You can test your agent in a {ref}`local Python environment <testing_agents_locally>` or in a {ref}<local development cluster `testing_agents_in_a_local_development_cluster`>. | ||
You can test your agent in a {ref}`local Python environment <testing_agents_locally>` or in a {ref}`local development cluster <testing_agents_in_a_local_development_cluster>`. | ||
|
||
### 3. Build a new Docker image | ||
|
||
The following is a sample Dockerfile for building an image for a Flyte agent: | ||
|
||
```Dockerfile | ||
FROM python:3.9-slim-buster | ||
FROM python:3.10-slim-bookworm | ||
|
||
MAINTAINER Flyte Team <[email protected]> | ||
LABEL org.opencontainers.image.source=https://github.com/flyteorg/flytekit | ||
|
||
WORKDIR /root | ||
ENV PYTHONPATH /root | ||
|
||
# additional dependencies for running in k8s | ||
RUN pip install prometheus-client grpcio-health-checking | ||
# flytekit will autoload the agent if package is installed. | ||
RUN pip install flytekitplugins-bigquery | ||
CMD pyflyte serve agent --port 8000 | ||
|
@@ -193,7 +192,7 @@ By running agents independently, you can thoroughly test and validate your agent | |
controlled environment before deploying them to the production cluster. | ||
|
||
By default, all agent requests will be sent to the default agent service. However, | ||
you can route particular task requests to designated agent services by adjusting the FlytePropeller configuration. | ||
you can route particular task requests to designated agent services by adjusting the FlytePropeller configuration. | ||
|
||
```yaml | ||
plugins: | ||
|
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