Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

set the channel topic: Working group for custom GPU types

set the channel description: <https://github.com/flyteorg/flyte/discussions/3796>

<@UNZB4NW3S> for naming suggestions - thinking about adding this field.  okay?  <https://github.com/flyteorg/flyteidl/pull/419/files#diff-8bd2613bf781125f77247c29a2f5502658c63cccf2b597a9ec3695ef1e7b2ca9R37>

background - the reason for adding an additional field rather than a custom resource enum, is that we are thinking the UX on the front-end will look something like
```@task
def t(requests=Resources(gpu="1", gpu_type="A100")): ...```
or something like that.

if we add a custom resource type, it felt a bit weird that if a user just specifies that, you end up with two elements in the ResourceEntry

I like the `Resources(gpu="1", gpu_type="A100")` UX for the user. The mapping from “A100” to node selectors/tolerations is defined by platform engineers e.g. in the helm values?