elegant-sandwich-48375
07/29/2025, 9:46 AMjolly-florist-66728
07/29/2025, 9:46 AMjolly-florist-66728
07/29/2025, 9:47 AMjolly-florist-66728
07/29/2025, 10:05 AMkubectl in the namespace where your Flyte project runs. For example, run:
kubectl get flyteworkflows.flyte.lyft.com -A
This command lists all FlyteWorkflow CRD instances across all namespaces. To inspect a specific workflow, use:
kubectl describe flyteworkflows.flyte.lyft.com workflow-name -n namespace
Would you like more detail on interpreting the CRD fields or troubleshooting specific issues?
Sources:
- FlytePropeller Architecture
- FlyteWorkflow CRD Example π 0 button π 0 button π‘ Hint: Mention @runllm in the thread for followups.jolly-florist-66728
07/29/2025, 10:13 AMjolly-florist-66728
07/29/2025, 11:11 AMkubectl describe flyteworkflows.flyte.lyft.com workflow-name -n namespace
This shows the workflow's spec (DAG, nodes) and status (phases, errors, timestamps). Look for the status section for node/task phases and error messages.
2. Check Pod Status:
List pods in the namespace to see if any are stuck or failed:
kubectl get pods -n namespace
Describe a pod for more details:
kubectl describe pod pod-name -n namespace
3. Use Flyte UI or CLI:
- In the Flyte UI, navigate to the workflow execution to view the execution graph, node statuses, logs, and errors.
- With Flytectl, run:
flytectl get execution -p project -d domain execid --details
This provides node/task execution details and log links.
4. Check Logs:
Access logs for FlytePropeller and task pods for error messages.
Would you like a step-by-step example with sample output or more detail on interpreting specific fields?
Sources:
- FlytePropeller Architecture
- Debugging Executions
- Inspecting Executions π 0 button π 0 button π‘ Hint: Mention @runllm in the thread for followups.average-finland-92144
07/31/2025, 4:31 PMjolly-florist-66728
08/14/2025, 12:54 PMjolly-florist-66728
08/14/2025, 12:55 PMjolly-florist-66728
08/14/2025, 12:58 PMjolly-florist-66728
08/14/2025, 12:59 PMeks.amazonaws.com/role-arn on the service account used by FlytePropeller, as shown in eks-production.yaml. The AWS SDK in FlytePropeller should then automatically refresh tokens, but if the pod is not using the correct service account or the IAM role is misconfigured, token refresh may fail.
To determine if you are using Flyte Binary or a different installation, check your deployment method:
- If you installed using the flyte-binary Helm chart or see a single pod running all Flyte components (admin, propeller, datacatalog, console), you are using Flyte Binary.
- If you see separate pods for flyteadmin, flytepropeller, datacatalog, etc., you are using the multi-component (core) installation, often deployed with the flyte-core Helm chart.
You can also check your Helm releases with helm list -n <namespace> and look for flyte-binary or flyte-core.
Would you like step-by-step instructions to check your service account and IAM role configuration?
Sources:
- Flyte binary vs core discussion
- eks-production.yaml π 0 button π 0 button π‘ Hint: Mention @runllm in the thread for followups.jolly-florist-66728
08/14/2025, 1:02 PMjolly-florist-66728
08/14/2025, 1:03 PMkubectl get serviceaccount <propeller-sa> -n <namespace> -o yaml
Look for the eks.amazonaws.com/role-arn annotation. Also, ensure your IAM role trust policy includes the EKS OIDC provider as described in AWS docs.
Would you like more detail on updating the service account or IAM role trust policy?
Sources:
- Flyte core Helm values π 0 button π 0 button π‘ Hint: Mention @runllm in the thread for followups.jolly-florist-66728
08/14/2025, 1:18 PMjolly-florist-66728
08/14/2025, 1:19 PMAccessDenied: Not authorized to perform sts:AssumeRoleWithWebIdentity. This means FlytePropeller (or the pod running the workflow) is unable to assume the IAM role via IRSA (IAM Roles for Service Accounts), so it cannot write to S3.
To resolve this, check the following:
1. The Kubernetes service account used by FlytePropeller (and/or task pods) must be annotated with the correct IAM role ARN (e.g., `eks.amazonaws.com/role-arn`).
2. The IAM role trust policy must allow the EKS OIDC provider and the service account as a principal.
3. The IAM role must have permissions for sts:AssumeRoleWithWebIdentity and S3 access.
You can check the service account annotation with:
kubectl get serviceaccount <propeller-sa> -n <namespace> -o yaml
and verify the IAM role trust policy in the AWS console.
Would you like step-by-step instructions for checking and fixing these settings?
Sources:
- https://github.com/flyteorg/flyte/issues/2417 π 0 button π 0 button π‘ Hint: Mention @runllm in the thread for followups.jolly-florist-66728
08/14/2025, 1:21 PMjolly-florist-66728
08/14/2025, 1:25 PMeks.amazonaws.com/role-arn: arn:aws:iam::089910700032:role/duploservices-kpmg). This is required for IRSA to work, allowing the pod to assume the specified IAM role and access AWS resources. If you are still seeing AccessDenied: Not authorized to perform sts:AssumeRoleWithWebIdentity, the issue is likely with the IAM role's trust policy or permissions.
Ensure the IAM role trust policy allows the EKS OIDC provider and the service account as a principal, and that the role has the necessary S3 and STS permissions. Would you like step-by-step instructions to verify and update the IAM role trust policy?
Sources:
- Flyte core Helm values π 0 button π 0 button π‘ Hint: Mention @runllm in the thread for followups.jolly-florist-66728
08/14/2025, 1:38 PMjolly-florist-66728
08/14/2025, 1:39 PMeks.amazonaws.com/role-arn. The actual token retrieval and refresh logic is managed by the AWS SDK, not by explicit FlytePropeller code. There is no explicit FlytePropeller code for fetching or refreshing WebIdentity tokens.
If you want to see where FlytePropeller interacts with AWS, you might look for S3 storage client initialization, but the token handling is abstracted by the SDK. Would you like more detail on where FlytePropeller initializes the S3 client or how the AWS SDK handles token refresh?
Sources:
- https://github.com/flyteorg/flyte/issues/5606
- https://github.com/flyteorg/flyte/issues/5012
Note: I wasnβt able to find highly relevant data sources, but above are a few potentially relevant links. π 0 button π 0 button π‘ Hint: Mention @runllm in the thread for followups.ancient-wolf-19325
09/03/2025, 10:12 AMancient-wolf-19325
09/03/2025, 10:13 AMlogger.level: 4 or higher). Then, review the FlytePropeller logs for messages about pod deletions or node aborts. The logs will typically include the workflow execution ID, node ID, and the reason for termination. For more on debugging executions and viewing logs, see Debugging Executions.
Would you like step-by-step instructions for changing the log level or examples of what to look for in the logs?
Sources:
- Debugging Executions π 0 button π 0 button π‘ Hint: Mention @runllm in the thread for followups.