From bfaa59a5212fad49d8107346b89faedc42ded09d Mon Sep 17 00:00:00 2001 From: Future-Outlier Date: Sun, 8 Sep 2024 11:49:06 +0800 Subject: [PATCH 1/2] Remove config in flyte agent' documentation Signed-off-by: Future-Outlier --- docs/flyte_agents/developing_agents.md | 22 ++++--------------- ...g_agents_in_a_local_development_cluster.md | 17 +------------- 2 files changed, 5 insertions(+), 34 deletions(-) diff --git a/docs/flyte_agents/developing_agents.md b/docs/flyte_agents/developing_agents.md index fd310088ef..aff54977a2 100644 --- a/docs/flyte_agents/developing_agents.md +++ b/docs/flyte_agents/developing_agents.md @@ -159,29 +159,15 @@ For flytekit versions `>v1.10.2`, use `pyflyte serve agent`. ### 4. Deploy Your Flyte agent -1. Update the FlyteAgent deployment's [image](https://github.com/flyteorg/flyte/blob/master/charts/flyteagent/templates/agent/deployment.yaml#L35) +Update the FlyteAgent deployment's [image](https://github.com/flyteorg/flyte/blob/master/charts/flyteagent/templates/agent/deployment.yaml#L35) ```bash kubectl set image deployment/flyteagent flyteagent=ghcr.io/flyteorg/flyteagent:latest ``` -2. Update the FlytePropeller configmap: - -```YAML - tasks: - task-plugins: - enabled-plugins: - - agent-service - default-for-task-types: - - bigquery_query_job_task: agent-service - - custom_task: agent-service -``` - -3. Restart FlytePropeller: - -``` -kubectl rollout restart deployment flytepropeller -n flyte -``` +:::{note} +Please make sure your propeller's image is >= 1.13.0 so that the propeller can automatically fetch the supported task types from your agent deployment. +::: ### 5. Canary deployment diff --git a/docs/flyte_agents/testing_agents_in_a_local_development_cluster.md b/docs/flyte_agents/testing_agents_in_a_local_development_cluster.md index 940385b2fb..211513f16e 100644 --- a/docs/flyte_agents/testing_agents_in_a_local_development_cluster.md +++ b/docs/flyte_agents/testing_agents_in_a_local_development_cluster.md @@ -41,26 +41,11 @@ flytectl demo start --dev pyflyte serve agent ``` -3. Update the config for the task handled by the agent in the single binary yaml file. +3. (Optional) Update the timeout configuration for each request to the agent deployment in the single binary YAML file: ```bash cd flyte vim ./flyte-single-binary-local.yaml ``` - -```yaml -:emphasize-lines: 9 -tasks: - task-plugins: - enabled-plugins: - - agent-service - - container - - sidecar - - K8S-ARRAY - default-for-task-types: - - sensor: agent-service - - container: container - - container_array: K8S-ARRAY -``` ```yaml plugins: # Registered Task Types From c65924e05df8e5cd5ba09c72ef81162c276c85fe Mon Sep 17 00:00:00 2001 From: Future-Outlier Date: Sun, 8 Sep 2024 15:03:53 +0800 Subject: [PATCH 2/2] Update docs/flyte_agents/developing_agents.md Co-authored-by: Kevin Su Signed-off-by: Future-Outlier --- docs/flyte_agents/developing_agents.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/flyte_agents/developing_agents.md b/docs/flyte_agents/developing_agents.md index aff54977a2..ea0d082c05 100644 --- a/docs/flyte_agents/developing_agents.md +++ b/docs/flyte_agents/developing_agents.md @@ -166,7 +166,7 @@ kubectl set image deployment/flyteagent flyteagent=ghcr.io/flyteorg/flyteagent:l ``` :::{note} -Please make sure your propeller's image is >= 1.13.0 so that the propeller can automatically fetch the supported task types from your agent deployment. +Please make sure your propeller's image version is >= 1.13.0 so that the propeller can automatically fetch the supported task types from your agent deployment. ::: ### 5. Canary deployment