Support taints during node creation

[jfeddern]

Hi there,

we would like to have the ability to add taints to a kubernetes node during the creation of a node.
Currently we have to add all taints after the kubernetes cluster is created. Which lead to some more or less complex terraform setup.

I would suggest to add this functionality to the ibm_container_worker_pool resource (https://ibm-cloud.github.io/tf-ibm-docs/v0.17.1/r/container_worker_pool.html)

Some other providers already support this solution (e.g. google https://www.terraform.io/docs/providers/google/r/container_cluster.html#taint)

[greglanthier]

This would be pretty handy. Some IKS best practice documents include steps to taint edge nodes to avoid having non-networking workloads scheduled on them (Securing Containers Workload Patterns in IKS is only one example).

It would be cool if we didn't need to run the following kubectl command after our clusters were created:

kubectl taint node -l dedicated=edge dedicated=edge:NoSchedule dedicated=edge:NoExecute

[hkantare]

The current version of IKS doesn't support any taint option. We will open a support ticket on IKS team for the requirement.

[sh0m1]

Since recently it is possible to taint all the nodes in a worker pool via ibmcloud cli command ibmcloud ks worker-pool taint set. Since there is the API support for this I would assume that there are no obstacles having terraform implementation of this in ibm_container_vpc_worker_pool resource?

[jfeddern]

#1646

[hkantare]

We will plan in next upcoming sprints