Skip to content

Add flyte agent in workflow-propeller#2657

Open
arjkrishnaTF wants to merge 3 commits intomainfrom
flyte_snowflake
Open

Add flyte agent in workflow-propeller#2657
arjkrishnaTF wants to merge 3 commits intomainfrom
flyte_snowflake

Conversation

@arjkrishnaTF
Copy link
Copy Markdown

@arjkrishnaTF arjkrishnaTF commented Apr 20, 2026

Note

Medium Risk
Introduces and enables a new in-cluster component (flyteagent) and changes propeller plugin routing, which can affect task execution behavior and requires correct secret/image configuration.

Overview
Enables Flyte’s agent-service task plugin and deploys/configures flyteagent as part of the tfy-workflow-propeller Helm chart (intended for Snowflake tasks).

Adds new values.yaml knobs for the propeller enabled_plugins routing (including mapping snowflake -> agent-service) and a new flyte-core.flyteagent block to configure the agent endpoint/TLS mode, custom image, service account annotations, secret material (snowflake_private_key), and resource requests/limits; updates the chart README.md to document these parameters.

Reviewed by Cursor Bugbot for commit 6a7fc41. Bugbot is set up for automated code reviews on this repo. Configure here.

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 6a7fc41. Configure here.

agent-service:
defaultAgent:
## @param flyte-core.flyteagent.plugin_config.plugins.agent-service.defaultAgent.endpoint to set the grpc endpoint propeller uses to reach the flyteagent service. Format: `k8s://<service>.<namespace>:<port>`.
endpoint: "k8s://flyteagent.{{ .Release.Namespace }}:8000"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Helm template expression in values.yaml won't be rendered

High Severity

The endpoint value "k8s://flyteagent.{{ .Release.Namespace }}:8000" contains a Helm template expression, but values.yaml is a plain YAML data file — Helm does not render template expressions within it. The {{ .Release.Namespace }} will be passed as a literal string to the flyte-core subchart. The upstream flyte-core chart's default for this field uses a hardcoded namespace (k8s://flyteagent.flyte:8000), strongly suggesting its configmap template does not use tpl to process this value. As a result, propeller will attempt to connect to a malformed endpoint and fail to reach the flyteagent service, breaking all agent-routed tasks (e.g., Snowflake).

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 6a7fc41. Configure here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant