Hey team.
Does anyone know what the license count is specifically looking for when identifying master vs worker?
We have a new issue where our masters are being identified as a worker and thus consuming our license count.
We (well... rke2) tag the following on our masters:
node-role.kubernetes.io/etcd=true
node-role.kubernetes.io/master=true
node-role.kubernetes.io/control-plane=true
Clarification - Master detection
Userlevel 1
Userlevel 7
+7
Userlevel 1
Friendly bump. :)
Userlevel 1
We appear to have resolved this by adding a taint to the Master nodes as follows:
kubectl taint node name-of-master-node-n node-role.kubernetes.io/master=:NoSchedule
Userlevel 7
+22
We appear to have resolved this by adding a taint to the Master nodes as follows:
kubectl taint node name-of-master-node-n node-role.kubernetes.io/master=:NoSchedule
That would make sense if the taint is not present I believe the kube-scheduler will schedule workoads on that node. It would seem to be the easiest way for K10 to check if a node needs to be licensed as well.
Comment
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.