Update helm chart deployment.yaml adding node taint

Azure / iot-edge-virtual-kubelet-provider

Kubernetes virtual kubelet provider for managing Azure IoT Edge deployments

MIT License

94 stars 25 forks source link

Update helm chart deployment.yaml adding node taint #7

Closed neumanndaniel closed 6 years ago

neumanndaniel commented 6 years ago

We need to taint the IoT VK node. Otherwise daemonsets will deploy pods on the IoT VK node. You do not want that. For the VK ACI connector we have this tainting.

veyalla commented 6 years ago

@neumanndaniel I noticed the behavior but didn't know about taints. I hacked around it by reducing pod capacity in virtual node to 3. This seems much cleaner, thanks!