New RunLLM response generated: >>>*# Question* Hi, I don't see proto file for pod backend plugin, so it means we are using json for communication? # Answer Yes, Flyte uses JSON for communication in the context of pod backend plugins. According to the Flyte backend plugins documentation, the

custom

field in the

TaskTemplate

is an unstructured JSON. This allows extending a task-template beyond the default supported targets, such as containers, by specifying additional information in a JSON structure. Would you like more detail? Sources: - Flyte backend plugins documentation Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1723019712.648319 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.