By boedy
As far as I know adding tags to your node pools in the DO Kubernetes dashboard will not add the same tags as labels to the nodes in the cluster.In our case we would like to dedicated a node per to certain workloads. Having to tag nodes individually seems not the way to go to be honest.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
So is this solved? I’ve just created node pool and it’s not in the cluster. Its 2020, should work right?
Seconded, this would make having multiple node pools much more useful. Currently, while I can manually label the nodes, node failure and replacement make it somewhat hard to guarantee the necessary labels are always there; being able to have labels automatically added to all nodes in a node pool would be really neat.
Try using the label beta.kubernetes.io/instance-type (eg. s-1vcpu-2gb or s-2vcpu-4gb) which represents the instance type you selected when you created the node pool. Find the instance type associated with your nodes as follows:
kubectl get nodes --show-labels
Then use the following nodeSelector to pick the instance type associated with your node pool as follows:
spec:
nodeSelector:
beta.kubernetes.io/instance-type: s-1vcpu-2gb
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.