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

[thomasjpfan]

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?

• [X] Yes

Have you read the Code of Conduct?

• [X] Yes

[eapolinario]

Let's investigate two (complementary) approaches:

1. validate podspec at registration time in flytekit
2. Use https://pkg.go.dev/k8s.io/kubernetes/pkg/apis/core/validation to validate podspecs in flyteadmin

[kevinliao852]

#take

[davidmirror-ops]

Hey @kevinliao852 I was wondering if you had any questions?

[kevinliao852]

Hey @davidmirror-ops , I just saw this message—sorry for the late reply! I previously discussed this with @pingsutw , and he suggested that adding the check in FlyteKit may not be necessary, so I’ve been focusing on FlyteAdmin instead. I’ve been looking into how validation can be best implemented there.

Do you have any thoughts on the approach for handling this validation? I'd appreciate any insights!

[davidmirror-ops]

Contributor's sync notes: once the bump to go 1.23 is merged, we can go back to use the validation library in flyteadmin

[github-actions[bot]]

"Hello 👋, this feature request has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 14 days. Thank you for your contribution and understanding! 🙏"

[kevinliao852]

I believe this issue is now unblocked because Go has already been upgraded to version 1.24.