search

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 to value.yaml and deployment.yaml with breaking changes for provider deployment #21

Closed neumanndaniel closed 5 years ago

neumanndaniel commented 5 years ago

Update deployment.yaml with breaking changes

If you are using the latest Virtual Kubelet image you get the following notification in the logs: Flag --taint has been deprecated, Taint key should now be configured using the VK_TAINT_KEY environment variable

So, the changes introduced are breaking changes, because the node taint has to be modified and some other spaces like the Virtual Kubelet port.

Furthermore a nodeSelector was added to make sure that the IoT Edge Provider will land on a Linux node in Kubernetes cluster with multiple agent pools having different node OS types.

Update value.yaml with breaking changes

So, the value.yaml is reflecting the changes that are made in the deployment.yaml.

rbac.install is switched now from false to true, because AKS cluster are deployed per default with Kubernetes RBAC enabled.

vk.image.tag is switched to latest from 0.3 to reflect the changes that are made to the deployment.yaml

Added the taint section.

neumanndaniel commented 5 years ago

I will update the example .yaml files for container deployment in the next days.

neumanndaniel commented 5 years ago

Updated the README.md and the sample-deployment.yaml and sample-pod.yaml to reflect the initial proposed changes for the IoT Edge Provider deployments.