flyteorg/flyte

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

Open

#6124 opened on Dec 26, 2024

View on GitHub
 (7 comments) (0 reactions) (1 assignee)Python (3,705 stars) (378 forks)batch import
enhancementhelp wanted

Description

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

Contributor guide

Tech stack
typescriptreactpython
Domain
full stack
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of Flyte PodTemplatesExperience with React and TypeScriptFamiliarity with Flyte propeller logs
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
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.