Daemonset pods stays in pending state

[harshalkwagh]

I installed "admission-webhook-server" by following the steps given in README.
Installation and normal functionality is working well but 1 side effect i observed is: When we create Daemonset in bound namespaces then pods for that daemonset stays in pending state.
Reason is it can not find nodeSelector label on the other nodes.

If there is any option to ignore node-binding for daemonsets then it will be really very helpful

[liangrog]

I think there are two things you found here:

1. the daemonset pod should only be scheduled on the nodes that bounded from your config for your namespace. So if it still scheduled to all nodes, then there might be a potential bug. It needs to be invesigate.

2. To ignore daemonset completely by adding a configuration option will be a new feature. Will consider it. But details will need to be investigate as there are many scenarios are to be considered, e.g. apply to all daemonsets or just a subset? if subset, what is the key to identify them?.

[liangrog]

feature and fixed are proposed in #4