Skip to main content
Solved

License Limit Exceeded because Kasten wrongly discovers 7 worker nodes instead of 4

  • November 17, 2023
  • 5 comments
  • 195 views
D

Good morning,

 

I have an issue on our testing environment where K10 discovers too many worker nodes in the cluster. It was working as expected prior the update to 6.0.7.

 

Is there a possibility to reset or fix this?

Here is the output of the nodes, as you can see we have 3 control-plane nodes an 4 worker nodes:

(⎈|oidc@play:kasten-io)]$ kubectl get nodes

NAME                        STATUS   ROLES           AGE    VERSION

k8s-play-m-0.domain   Ready    control-plane   544d   v1.24.14

k8s-play-m-1.domain   Ready    control-plane   544d   v1.24.14

k8s-play-m-2.domain   Ready    control-plane   544d   v1.24.14

k8s-play-w-0.domain   Ready    <none>          544d   v1.24.14

k8s-play-w-1.domain   Ready    <none>          544d   v1.24.14

k8s-play-w-2.domain   Ready    <none>          544d   v1.24.14

k8s-play-w-3.domain   Ready    <none>          544d   v1.24.14

Best answer by Geoff Burke

I believe you can restrict the nodes that K10 is used on by leveraging taints and tolerations.

Check this out here where they talk about Pinning K10 to Specific Nodes

https://docs.kasten.io/latest/install/advanced.html

 

However, I am not completely certain that this will affect the license count. Let’s see what the kasten folks say.

    Chris.Childerhose
    Geoff Burke
    Madi.Cristil

    5 comments

    Madi.Cristil
    Forum|alt.badge.img+8
    • Madi.Cristil
    • Community Manager
    • November 27, 2023

    @jaiganeshjk 

    Madi Cristil
    Geoff Burke
    Forum|alt.badge.img+22
    • Geoff Burke
    • Veeam Vanguard
    • Answer
    • November 27, 2023

    I believe you can restrict the nodes that K10 is used on by leveraging taints and tolerations.

    Check this out here where they talk about Pinning K10 to Specific Nodes

    https://docs.kasten.io/latest/install/advanced.html

     

    However, I am not completely certain that this will affect the license count. Let’s see what the kasten folks say.

    VMCA2024, VMCE2023, VMCE2024-SP,CKA, LFCS
    Hagag
    D
    Hagag
    Forum|alt.badge.img+2
    • Hagag
    • Experienced User
    • November 28, 2023

    @Daniel Moes 

    What was your old k10 version?  fine? Have there been any changes in your cluster configuration?

     

    D
    • Daniel Moes
    • Author
    • Comes here often
    • December 4, 2023

    I believe you can restrict the nodes that K10 is used on by leveraging taints and tolerations.

    Check this out here where they talk about Pinning K10 to Specific Nodes

    https://docs.kasten.io/latest/install/advanced.html

     

    However, I am not completely certain that this will affect the license count. Let’s see what the kasten folks say.

     

    Hello Geoff,

    It turns out, our control plane nodes were not tainted as such. I suppose this went wrong during a K8S update that was done pretty much at the same time as the Kasten update. So Kasten seems to check for the taints to identify the type of the node.

     

    I fixed it by adding the taint via kubectl:

    kubectl taint nodes node.domain node-role.kubernetes.io/control-plane:NoSchedule

    Thank you very much for pointing me in the right direction! 😀

    Geoff Burke
    Geoff Burke
    Forum|alt.badge.img+22
    • Geoff Burke
    • Veeam Vanguard
    • December 4, 2023

    I believe you can restrict the nodes that K10 is used on by leveraging taints and tolerations.

    Check this out here where they talk about Pinning K10 to Specific Nodes

    https://docs.kasten.io/latest/install/advanced.html

     

    However, I am not completely certain that this will affect the license count. Let’s see what the kasten folks say.

     

    Hello Geoff,

    It turns out, our control plane nodes were not tainted as such. I suppose this went wrong during a K8S update that was done pretty much at the same time as the Kasten update. So Kasten seems to check for the taints to identify the type of the node.

     

    I fixed it by adding the taint via kubectl:

    kubectl taint nodes node.domain node-role.kubernetes.io/control-plane:NoSchedule

    Thank you very much for pointing me in the right direction! 😀

    Glad to have helped. Cheers

    VMCA2024, VMCE2023, VMCE2024-SP,CKA, LFCS
    Terms & ConditionsAccessibility statement