From 31696cf550a5ffc68a6df44a0365ae942ab20042 Mon Sep 17 00:00:00 2001 From: Jason Parraga Date: Tue, 21 May 2024 16:27:01 +0000 Subject: [PATCH] Update FlyterPropeller config to working config for flyte agent --- docs/flyte_agents/developing_agents.md | 29 +++++++++++++++++++------- 1 file changed, 21 insertions(+), 8 deletions(-) diff --git a/docs/flyte_agents/developing_agents.md b/docs/flyte_agents/developing_agents.md index fe55630248a..95e661dcdea 100644 --- a/docs/flyte_agents/developing_agents.md +++ b/docs/flyte_agents/developing_agents.md @@ -169,13 +169,26 @@ kubectl set image deployment/flyteagent flyteagent=ghcr.io/flyteorg/flyteagent:l 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 +plugins: + agent-service: + defaultAgent: + endpoint: dns:///flyteagent..svc.cluster.local:8000 + supportedTaskTypes: + - sensor + - armada +tasks: + task-plugins: + default-for-task-types: + custom_task: agent-service + container: container + container_array: k8s-array + sensor: agent-service + sidecar: sidecar + enabled-plugins: + - container + - sidecar + - k8s-array + - agent-service ``` 3. Restart FlytePropeller: @@ -193,7 +206,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: