Supporting Taints in LKE Node Pools?

The managed node pools feature of LKE is a nice feature. I can use node selectors to target nodes for workloads, however, I would like to add taints to nodes in certain node pools to segment workloads using the taints/tolerations mechanism in Kubernetes.

This is a more flexible approach that doesn't require pinning to specific attributes of nodes. Today I see labels like lke.linode.com/pool-id and beta.kubernetes.io/instance-type which can be used to target based on the name of the pool or type of instance. If I want to segment workloads I have to know the dynamically-generated pool ID which is a bit of a pain to dig up.

In short, I feel that taints would be a more flexible option to allow clusters the flexibility we are used to in k8s.

Feature Request

When creating a node pool, I would like to be able to specify a list of taints to apply to nodes in the pool. These taints would automatically be added to the nodes, and would prevent workloads without the corresponding toleration from running on them.

I'd expect this to be added to the Linode API LKE Pools endpoints, as well as the Terraform provider.

Another option would be to allow for some additional Kubelet args which include things like taints, but this would be a pretty dirty API.

Examples in the Wild

The following are good examples of this kind of node-level customization. Additional labels, or naming of pools could also make it even easier to assign workloads to nodes.

• GKE Node Taints
• DO Node Taints

Any plans to add this feature?