Split contiv etcd and etcd-proxy into two daemonsets

Putting contiv etcd and etcd-proxy into the same daemonset and manage
the difference by a env file is not good for scaling (adding nodes).
This commit split them into two daemonsets so that when adding nodes,
k8s could automatically starting a etcd-proxy on new nodes without need
to run related play that putting env file.

roles/network_plugin/contiv/tasks/main.yml

@@ -21,6 +21,7 @@
   template:
     src: contiv-etcd.env.j2
     dest: "{{ contiv_etcd_conf_dir }}/contiv-etcd.env"
+  when: inventory_hostname in groups['kube-master']
 
 - set_fact:
     contiv_config_dir: "{{ contiv_config_dir }}"
@@ -38,6 +39,7 @@
       - {name: contiv-netplugin, file: contiv-netplugin-clusterrole.yml, type: clusterrole}
       - {name: contiv-netplugin, file: contiv-netplugin-serviceaccount.yml, type: serviceaccount}
       - {name: contiv-etcd, file: contiv-etcd.yml, type: daemonset}
+      - {name: contiv-etcd-proxy, file: contiv-etcd-proxy.yml, type: daemonset}
       - {name: contiv-netplugin, file: contiv-netplugin.yml, type: daemonset}
       - {name: contiv-netmaster, file: contiv-netmaster.yml, type: daemonset}