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
Is your feature request related to a problem?/Why is this needed
I would need support for "Tainted" kubernetes nodes.
I'm running the yaml-files on my AKS cluster, and the nodes where I would need the nvme storage are tainted, to only allow "certain" pods to run. Obvisouly the local-volume-provisioner-*** pods do not have the necessary tolerations, so they are not allowed to run on my tainted nodes.
Describe the solution you'd like in detail
An example of how to tolerate the pods, so they are allowed to run on my tainted nodes
Describe alternatives you've considered
Untainting my nodes, but this would lead to other problems
Additional context
The taints are necessary , because the software, running on the AKS cluster , needs those taints, and I cannot change those
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?/Why is this needed
I would need support for "Tainted" kubernetes nodes.
I'm running the yaml-files on my AKS cluster, and the nodes where I would need the nvme storage are tainted, to only allow "certain" pods to run. Obvisouly the local-volume-provisioner-*** pods do not have the necessary tolerations, so they are not allowed to run on my tainted nodes.
Describe the solution you'd like in detail
An example of how to tolerate the pods, so they are allowed to run on my tainted nodes
Describe alternatives you've considered
Untainting my nodes, but this would lead to other problems
Additional context
The taints are necessary , because the software, running on the AKS cluster , needs those taints, and I cannot change those
The text was updated successfully, but these errors were encountered: