K8s GPU nodes are already kind of an example of this-- the app can still access the specialty capabilities of the hardware, we just have to make sure to tell the scheduler "hey run this app on this kind of node with this flavor of capabilities". I could imagine that kind of flavor capability growing and becoming more fleshed out
Except k8s calls it 'taints' which is uh a weird choice.
Taints is a funny name when you look at it like that but taints are actually the opposite half of the story.
If you want a Pod to be scheduled with a certain node you need to add affinity.
The taints are to ensure that your average nginx pod doesn't run on the specialty hardware and block the pods that actually need it. In theory the scheduler could be smart enough to evict the pods that don't need the special node but IDK if the kube scheduler is smart enough. Even then it may he preferable to have the taint though to reduce the eviction rate.
Except k8s calls it 'taints' which is uh a weird choice.