This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 10 days.

Based on the code the maintainer for gpu feature discovery mentioned in the related issue, I want to say that the output from nvidia.com/gpu.product is exactly the same as what you get from running nvidia-smi --query-gpu=name --format=csv,noheader,nounits as done here? the only difference being there's dashes instead of spaces. On my machine I get the following outputs

$ kubectl describe node | grep nvidia.com/gpu.product
                    nvidia.com/gpu.product=NVIDIA-H100-80GB-HBM3

$ nvidia-smi --query-gpu=name --format=csv,noheader,nounits
NVIDIA H100 80GB HBM3

so it's probably enough to use similar logic as the labeler job to compare against the canonical gpu names we have?

I can draft up a PR for this. it was getting hard to remember to rerun the labeler job anytime I added a node to my k3s cluster but this way it just works directly with feature discovery. Somewhat resolves #3432 if people are running with the NVIDIA gpu operator

Good point, if the nvidia.com/gpu.product label indeed uses nvidia-smi --query-gpu=name --format=csv,noheader,nounits with - instead of , we should be able to have a GPULabelFormatter that parses GFD labels into SkyPilot canonical names. Would love to see a PR. Just noting that we will need to test it extensively, since having a half-functioning label formatter is worse than having users run the labelling script for consistency.