flyteorg/flyte

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

Open

#6,124 opened on 2024年12月26日

GitHub で見る
 (7 comments) (0 reactions) (1 assignee)Python (3,705 stars) (378 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.