flyteorg/flyte

[Core feature] Surface pod template mis-configuration in the UI.

Open

#6,124 建立於 2024年12月26日

在 GitHub 查看
 (7 留言) (0 反應) (1 負責人)Python (3,705 star) (378 fork)batch import
enhancementhelp wanted

描述

Motivation: Why do you think this is important?

When working with PodTemplates any misconfiguration do not show up in the UI. The UI only shows "pending". The only way to debug it is to see the propeller logs.

Goal: What should the final outcome look like, ideally?

The errors related to pod template misconfiguration are show in the UI.

Describe alternatives you've considered

We can also do the same type of validation on the client side so we error early.

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

  • Yes

Have you read the Code of Conduct?

  • Yes

貢獻者指南

技術棧
typescriptreactpython
領域
full stack
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Understanding of Flyte PodTemplatesExperience with React and TypeScriptFamiliarity with Flyte propeller logs
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
The issue requests surfacing pod template misconfiguration errors in the UI. Currently, errors are only visible in propeller logs. The solution involves both backend and frontend changes. First, investigate how flytepropeller processes PodTemplates and where errors occur. Then, propose a way to propagate these errors to the UI via API. On the frontend, find where 'pending' status is displayed (likely in flyteconsole) and add error display components. Note that the issue has an assignee, so any work should coordinate with them.
[Core feature] Surface pod template mis-configuration in the UI. · flyteorg/flyte#6124 | Good First Issue