Hi all, can anyone help me getting Flyte agent and...
# flyte-supporto
orange-army-92143
03/26/2025, 2:54 PMHi all, can anyone help me getting Flyte agent and FileSensor up and running in my sandbox environment? Hitting an error when running this example workflow in the user guide. More details in the thread.
Copy code
Workflow[flytesnacks:development:<http://sensor.file_sensor_example.wf|sensor.file_sensor_example.wf>] failed. RuntimeExecutionError: max number of system retry attempts [11/10] exhausted. Last known status message: failed at Node[n0]. RuntimeExecutionError: failed during plugin execution, caused by: failed to execute handle for plugin [container]: [BadTaskSpecification] invalid TaskSpecification, unable to determine Pod configurationorange-army-92143
03/26/2025, 2:55 PMI have the Flyte agent deployed in our sandbox environment using the flyte-binary helm chart, and the flyte agent appears healthy based on k8s logs and status and believe I have the config correct according to Flyte's docs
Output from k9s:
Copy code
│ Data │
│ ==== │
│ 001-plugins.yaml: │
│ ---- │
│ tasks: │
│ task-plugins: │
│ default-for-task-types: │
│ container: container │
│ container_array: k8s-array │
│ sensor: agent-service │
│ sidecar: sidecar │
│ enabled-plugins: │
│ - container │
│ - sidecar │
│ - k8s-array │
│ - agent-service │
│ - echo │
│ plugins: │
│ logs: │
│ kubernetes-enabled: false │
│ cloudwatch-enabled: false │
│ stackdriver-enabled: false │
│ k8s: │
│ co-pilot: │
│ image: "<http://cr.flyte.org/flyteorg/flytecopilot-release:v1.15.0|cr.flyte.org/flyteorg/flytecopilot-release:v1.15.0>" │
│ k8s-array: │
│ logs: │
│ config: │
│ kubernetes-enabled: false │
│ cloudwatch-enabled: false │
│ stackdriver-enabled: false │
│ agent-service: │
│ defaultAgent: │
│ defaultTimeout: 10s │
│ endpoint: <k8s://flyteagent.flyte:8000> │
│ insecure: true │
│ timeouts: │
│ GetTask: 10sorange-army-92143
03/26/2025, 2:56 PMI'm seeing the following the flyte-agent logs. "Is Sync" is set to False. Unsure if that means things are not configured correctly.
orange-army-92143
03/26/2025, 2:57 PMMy helm looks something like:
Copy code
flyteagent:
enabled: true
enabled_plugins:
tasks:
task-plugins:
enabled-plugins:
- container
- sidecar
- k8s-array
- agent-service
- echo
default-for-task-types:
- container: container
- sidecar: sidecar
- container_array: k8s-array
- sensor: agent-serviceorange-army-92143
03/26/2025, 2:57 PMAny thoughts here to debug this further?
orange-army-92143
03/26/2025, 8:56 PMI was able to get FileSensor working locally using the standard example. The issue ended up being with the image I was using in the environment that didn't have the runtime set up properly.
orange-army-92143
03/26/2025, 8:58 PMIs there a way with FileSensor to pass the file path that triggered the workflow to the following task (to support downloading that file in the following task)?
Is there a way to support sensing a wild card? that is, trigger off any file added to an s3 bucket?
Thanks!
a
average-finland-92144
03/27/2025, 3:37 PM@orange-army-92143 unfortunately right now seems like FileSensor only returns a boolean and doesn't output the path but the base class could be extended to do so. That'd be a great contribution 🙂
average-finland-92144
03/27/2025, 3:39 PMIs there a way to support sensing a wild card? that is, trigger off any file added to an s3 bucket?not really, this again would require extending the base class
6 Views