Feature Request: UI Integration to Apply Taints automatically to Node Pools

[digitalocean]

Feature Request: UI Integration to Apply Taints automatically to Node Pools

[timoreimann]

Hi @joeldeteves 👋

While we don't have UI / control panel integration yet, it is possible to specify so-called persistent node pool taints through the API that have the very behavior you are describing. See also the taints field on the DOKS API reference.

Does that help you, or were you asking for UI integration in particular?

[joeldeteves]

Hi @joeldeteves 👋

While we don't have UI / control panel integration yet, it is possible to specify so-called persistent node pool taints through the API that have the very behavior you are describing. See also the taints field on the DOKS API reference.

Does that help you, or were you asking for UI integration in particular?

UI integration would definitely make things easier.

But regarding the option you showed me, is it possible to apply a persistent node pool taint to an existing node pool?

Currently I only see it under the add section of that document.

Nevermind, I see it under the update section as well!

Thank you,

[timoreimann]

Great! I'm happy to keep the issue open to publicly track UI integration.

[joeldeteves]

Here's how I did it in case anyone else is searching for a quick solution:

1. export $DIGITALOCEAN_TOKEN=my-access-token
2. doctl -t $DIGITALOCEAN_TOKEN kubernetes cluster node-pool update mycluster mynodepool --taint "key=false:NoExecute"

Using doctl is a bit easier than using cURL or other methods to access the API.

Docs on how to use doctl here: https://docs.digitalocean.com/reference/doctl/reference/kubernetes/cluster/node-pool/update/

Thanks again @timoreimann

[timoreimann]

Related: #3