You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to update our clusters to v2, but I am having trouble with the node labels. I think using labels (and possibly taints) on a cluster with include_instance_type_in_instance_name enabled is currently not possible. It works fine on masters, though. These are the last few lines of output:
[Instance test-cx22-pool-asdf-worker1] [INFO] systemd: Starting k3s-agent
[Instance test-cx22-pool-asdf-worker1] ...k3s has been deployed to worker test-cx22-pool-asdf-worker1.
[Node labels]
Adding labels to masters_pool pool workers...
[Node labels] node/test-cx22-master1 not labeled
[Node labels] ...node labels applied
[Node labels]
Adding labels to asdf pool workers...
error: resource(s) were provided, but no name was specified
[Node labels] : error: resource(s) were provided, but no name was specified
I also did some digging and I think the issue might be related to this line of code, as it does not check for the configured naming scheme. Not sure, though.
Workaround: I just removed the labels and taints from the config file. Existing labels and taints will not be removed from the nodes.
This is the config I used for testing. (I'm using an existing network.)
Thanks for reporting this! It must have slipped during upgrade testing. Glad you figured out a workaround for now. I will fix this in the upcoming release, unless you are willing to make a PR for it :)
I'm trying to update our clusters to v2, but I am having trouble with the node labels. I think using labels (and possibly taints) on a cluster with
include_instance_type_in_instance_name
enabled is currently not possible. It works fine on masters, though. These are the last few lines of output:I also did some digging and I think the issue might be related to this line of code, as it does not check for the configured naming scheme. Not sure, though.
Workaround: I just removed the labels and taints from the config file. Existing labels and taints will not be removed from the nodes.
This is the config I used for testing. (I'm using an existing network.)
cluster.yaml
The text was updated successfully, but these errors were encountered: