Allow KnownGPUVendors customization

[zulhfreelancer]

Is your feature request related to a problem? Please describe.
Thanks for adding GPUs to nodes view (link to issue). Would it be possible to allow k9s users to customize the KnownGPUVendors map (link to code)?

Describe the solution you'd like
My nodes have GPUs. But they are not prefixed with nvidia.com/gpu. I'm looking for ways to customize the KnownGPUVendors i.e. using k9s config file.

k9s:
  known_gpu_vendors: something.com/foo,something.net,foo.something.org,something.io/foo/bar

In this case, the list is comma separated. I'm fine with any separator/delimeter as long as it's not dot or slash.

If the .known_gpu_vendors is not defined, defaults to the hard coded map defined in current v0.50.7 release.

Describe alternatives you've considered
None

Additional context
None

[derailed]

@zulhfreelancer Indeed! That is the next logical step. I do think this new configuration should just be additive to the known list as likely users will extend the list and not redefine it pending how node opt to advertise the gpu vendor.
Would this make sense?

[zulhfreelancer]

Yeah, that makes sense

[BroderPeters]

I'm very excited to see movement around GPU visibility in k9s!
Not having looked that deep into the implementation, I would be curious to know how you feel about automatic detection of NVIDIA MIGs?
According to this issue I get that I could potentially add all possible MIG options to the config as additional vendors, but it also might be a bit of a hustle.

One example of a node in this scenario might be one having 2 H100 NVIDIA GPUs. One being run as a full GPU and one being run by some MIG logic. That would result to the following node labels:
(truncated it a bit for clearness)

      nvidia.com/gpu.count: "1"
[...]
      nvidia.com/mig-1g.10gb.count: "2"
      nvidia.com/mig-1g.10gb.engines.copy: "1"
      nvidia.com/mig-1g.10gb.engines.decoder: "0"
      nvidia.com/mig-1g.10gb.engines.encoder: "0"
      nvidia.com/mig-1g.10gb.engines.jpeg: "0"
      nvidia.com/mig-1g.10gb.engines.ofa: "0"
      nvidia.com/mig-1g.10gb.memory: "9728"
      nvidia.com/mig-1g.10gb.multiprocessors: "14"
      nvidia.com/mig-1g.10gb.product: NVIDIA-A100-80GB-PCIe-MIG-1g.10gb
      nvidia.com/mig-1g.10gb.replicas: "1"
      nvidia.com/mig-1g.10gb.slices.ci: "1"
      nvidia.com/mig-1g.10gb.slices.gi: "1"
      nvidia.com/mig-2g.20gb.count: "1"
[...]
      nvidia.com/mig-3g.40gb.count: "1"
[...]
      nvidia.com/mig.capable: "true"
      nvidia.com/mig.config: all-balanced
      nvidia.com/mig.config.state: success
      nvidia.com/mig.strategy: mixed
      nvidia.com/gpu: "0"
      nvidia.com/mig-1g.10gb: "2"
      nvidia.com/mig-2g.20gb: "1"
      nvidia.com/mig-3g.40gb: "1"
      nvidia.com/gpu: "0"
      nvidia.com/mig-1g.10gb: "2"
      nvidia.com/mig-2g.20gb: "1"
      nvidia.com/mig-3g.40gb: "1"