@ancient-wolf-19325 Executions is not working, pod is not created. In the flyte ui task status is showing as queued and not changing. Below are flyepropeller logs: E1214 082200.714965 1 workers.go:103] error syncing 'kaas-pipeline-4321-development/try111': failed at Node[n0]. RuntimeExecutionError: failed during plugin execution, caused by: failed to execute handle for plugin [container]: [Invalid] failed to create resource, caused by: Pod "try111-n0-0-n0-0" is invalid: [spec.containers[0].env[0].valueFrom: Invalid value: "": may not be specified when

value

is not empty, spec.containers[0].env[1].valueFrom: Invalid value: "": may not be specified when

value

is not empty, spec.containers[0].env[2].valueFrom: Invalid value: "": may not be specified when

value

is not empty]

It seems likely that the issue you're encountering is related to the environment variables configuration in your Flyte task. The error message indicates that there are invalid

valueFrom

fields specified for environment variables in the pod's container specification. This typically happens when both

value

and

valueFrom

are set for the same environment variable, which is not allowed. Based on this GitHub issue, it might be helpful to review your task's environment variable settings to ensure that each variable is either using

value

or

valueFrom

, but not both. You may need to adjust your task configuration to resolve this conflict. Would you like more detailed guidance on how to adjust your task configuration or further investigate this issue? Sources: - Flyte GitHub Issue #5273 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 i found the problem.. kyverno cluster policy is adding the same key as env with valuefrom and while exeutions api i am adding same key with value which contradicting

I'm here to help with questions related to Flyte. It seems like you've identified a conflict between your Kyverno cluster policy and the environment variables you're setting in your Flyte task. If you have any questions about Flyte or need further assistance with configuring your Flyte tasks, feel free to ask! 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.