Feature/tolerations

[awalford16]

Add support for node tolerations through TOLERATIONS env variable, in the format of key=value:NoSchedule

❯ k get node aks-gpu4cpu-15439062-vmss00001o -o yaml | yq .spec.taints
- effect: NoSchedule
  key: sku
  value: gpu

❯ k get pods -o wide | grep image
kubernetes-image-puller-4vs98                                  3/3     Running     0               9m25s   10.244.12.8   aks-gpu4cpu-15439062-vmss00001o     <none>           <none>
kubernetes-image-puller-54wtr                                  3/3     Running     0               9m25s   10.244.8.8    aks-gpu4cpu-15439062-vmss00001m     <none>           <none>
kubernetes-image-puller-84t4d                                  3/3     Running     0               9m25s   10.244.7.8    aks-gpu4cpu-15439062-vmss00001l     <none>           <none>

❯ k get pod kubernetes-image-puller-4vs98 -o yaml | yq .spec.tolerations
- effect: NoSchedule
  key: sku
  operator: Equal
  value: gpu
- effect: NoExecute
  key: node.kubernetes.io/not-ready
  operator: Exists
- effect: NoExecute
  key: node.kubernetes.io/unreachable
  operator: Exists
- effect: NoSchedule
  key: node.kubernetes.io/disk-pressure
  operator: Exists
- effect: NoSchedule
  key: node.kubernetes.io/memory-pressure
  operator: Exists
- effect: NoSchedule
  key: node.kubernetes.io/pid-pressure
  operator: Exists
- effect: NoSchedule
  key: node.kubernetes.io/unschedulable
  operator: Exists

[github-actions]

Click here to review and test in web IDE:

[ibuziuk]

@dkwon17 could you please review

[ibuziuk]

Thank you for the contribution, but we consider merging #165 once the conflicts are resolved since it looks more configurable

[dkwon17]

Thank you @awalford16 , we decided to merge #162 because it allows configuring the operator field, as well as allowing omitting certain fields like key, effect etc.