https://flyte.org logo
Join Slack
Powered by
:thread: I'm having trouble getting flyte propelle...
# ask-the-community
j
🧵 I'm having trouble getting flyte propeller to talk to the agent service for a custom task.
flyte propeller complains about having no plugin for 
armada
Copy code
❯ kubectl logs flytepropeller-5559db6f4d-bgpr7 -f | grep armada                                                                                                                                                            
{"json":{"exec_id":"f6bf36697f1a84994907","node":"examplesayhello","ns":"flytesnacks-development","res_ver":"32767965","routine":"worker-0","tasktype":"armada","wf":"flytesnacks:development:.flytegen.example.say_hello"},"level":"warning","msg":"No plugin found for Handler-type [armada], defaulting to [container]","ts":"2024-05-16T01:07:14Z"}
{"json":{"exec_id":"f6bf36697f1a84994907","node":"examplesayhello","ns":"flytesnacks-development","res_ver":"32767966","routine":"worker-0","tasktype":"armada","wf":"flytesnacks:development:.flytegen.example.say_hello"},"level":"warning","msg":"No plugin found for Handler-type [armada], defaulting to [container]","ts":"2024-05-16T01:07:14Z"}
However I have configured it to consult the agent service for task type 
armada
Copy code
❯ kubectl exec --stdin --tty flytepropeller-5559db6f4d-bgpr7 -- /bin/sh                                                                                                                                                           
~ $ cat /etc/flyte/config/enabled_plugins.yaml 
tasks:
  task-plugins:
    default-for-task-types:
      armada: agent-service
      container: container
      container_array: k8s-array
      sensor: agent-service
      sidecar: sidecar
    enabled-plugins:
    - container
    - sidecar
    - k8s-array
    - agent-service
Looks like I need something like this
Copy code
~ $ cat /etc/flyte/config/enabled_plugins.yaml 
plugins:
  agent-service:
    defaultGrpcEndpoint: flyteagent.flyte.svc.cluster.local:8000
    supportedTaskTypes:
    - sensor
    - armada
tasks:
  task-plugins:
    default-for-task-types:
      armada: agent-service
      container: container
      container_array: k8s-array
      sensor: agent-service
      sidecar: sidecar
    enabled-plugins:
    - container
    - sidecar
    - k8s-array
    - agent-service
Based on some slack history I found: https://discuss.flyte.org/t/16032161/hey-flyte-gang-wave-i-am-currently-trying-to-enable-file-sen
At least now I'm getting some gRPC errors as if propeller is trying to talk to the agent service but wow this is frustrating. Not documented in the main docs or even the helm chart.
k
this is old config
Copy code
plugins:
  agent-service:
    defaultGrpcEndpoint: flyteagent.flyte.svc.cluster.local:8000
    supportedTaskTypes:
    - sensor
    - armada
should be
Copy code
plugins:
  agent-service:
    defaultAgent:
      endpoint: <endpoint>
    supportedTaskTypes:
    - sensor
    - armada
j
I will put up some doc PRs tomorrow probably. And hopefully we can upstream some of our helm chart changes. The agent is pretty unconfigurable in helm right now
k
awesome, thanks. ping me once you create a PR. I’ll review ASAP
j
Coming back to configuring the agent. I was looking at the 
flyte
helm chart which I now realize is for sandbox purposes per the docs. The 
flyte-core
helm chart actually has a dedicated config options for the flyte agent which is much appreciated.
Alright so I configured the flyte agent per the 
flyte-core
helm chart and now it won't handle the 
armada
task again.
Copy code
~ $ cat /etc/flyte/config/agent_service.yaml 
plugins:
  agentService:
    defaultAgent:
      endpoint: dns:///flyteagent.flyte-data-plane.svc.cluster.local:8000
      insecure: true
~ $ cat /etc/flyte/config/enabled_plugins.yaml 
tasks:
  task-plugins:
    default-for-task-types:
      armada: agent-service
      container: container
      container_array: k8s-array
      sensor: agent-service
      sidecar: sidecar
    enabled-plugins:
    - container
    - sidecar
    - k8s-array
    - agent-service
I'm wondering if the helm chart needs to be updated to reflect the config that worked @Kevin Su
Yeah maybe so. That part of the helm chart appears to be 2 years old so probably out of date
Open in Slack
PreviousNext
Powered by